ࡱ > p r m n o #` bjbjmm n C S 6 6 6 6 6 6 6 $ Z P 6 Z ڏ d d Ȕ Ȕ Ȕ } x j l l l l l l $ h
b 6 6 6 Ȕ Ȕ % % % | 6 Ȕ 6 Ȕ j % j % % n 6 6 Ȕ Ώ еX# q ( 0 6 o o P o 6 % X Z Z d M b` + Z Z b` Z Z Z 6 6 6 6 6 6
Service Component Architecture JCA Binding Specification Version 1.1
Committee Draft 01
7th August, 2008
Specification URIs:
This Version:
HYPERLINK "http://docs.oasis-open.org/opencsa/sca-bindings/sca-jcabinding-1.1-spec-cd01.html" http://docs.oasis-open.org/opencsa/sca-bindings/sca-jcabinding-1.1-spec-cd01.html
HYPERLINK "" HYPERLINK "http://docs.oasis-open.org/opencsa/sca-bindings/sca-jcabinding-1.1-spec-cd01.doc" http://docs.oasis-open.org/opencsa/sca-bindings/sca-jcabinding-1.1-spec-cd01.doc
HYPERLINK "http://docs.oasis-open.org/opencsa/sca-bindings/sca-jcabinding-1.1-spec-cd01.pdf" http://docs.oasis-open.org/opencsa/sca-bindings/sca-jcabinding-1.1-spec-cd01.pdf (Authoritative)
Previous Version:
Latest Version:
HYPERLINK "http://docs.oasis-open.org/opencsa/sca-bindings/sca-jcabinding-1.1-spec.html" http://docs.oasis-open.org/opencsa/sca-bindings/sca-jcabinding-1.1-spec.html
HYPERLINK "http://docs.oasis-open.org/opencsa/sca-bindings/sca-jcabinding-1.1-spec.doc" http://docs.oasis-open.org/opencsa/sca-bindings/sca-jcabinding-1.1-spec.doc
HYPERLINK "http://docs.oasis-open.org/opencsa/sca-bindings/sca-jcabinding-1.1-spec.pdf" http://docs.oasis-open.org/opencsa/sca-bindings/sca-jcabinding-1.1-spec.pdf (Authoritative)
Latest Approved Version:
Technical Committee:
HYPERLINK "http://www.oasis-open.org/committees/sca-bindings"OASIS Service Component Architecture / Bindings (SCA-Bindings) TC
Chair(s):
Simon Holdsworth, IBM
Editor(s):
Simon Holdsworth, IBM
Khanderao Kand, Oracle
Anish Karmarkar, Oracle
Sanjay Patil, SAP
Piotr Przybylski, IBM
Related work:
This specification replaces or supercedes:
Service Component Architecture JCA Binding Specification Version 1.00 20 September 2007
This specification is related to:
Service Component Architecture Assembly Model Specification Version 1.1
Service Component Architecture Policy Framework Specification Version 1.1
Declared XML Namespace(s):
http://docs.oasis-open.org/ns/opencsa/sca/200712
Abstract:
This document presents bindings describing access and connectivity to the services provided by the Enterprise Information System (EIS).
This version of the document describes JCA Bindings thus narrowing connectivity down to the connectivity to the EIS system external to the SCA system, based on the Java EE Connector Architecture specification and implemented in Java.
Further specification is necessary to define EIS Bindings between different SCA runtimes within SCA system, for example J2EE and EIS based runtimes.
The binding specified in this document applies to the composites references and services.
The connection to exchange data with the EIS is characterized by two sets of configuration parameters, the connection and interaction parameters. The former set determines the location of the target system the latter determines characteristics that need to be specified to invoke one specific service available at the endpoint. JCA Binding model captures these parameters as separate sets to allow their reuse and reconfiguration.
Status:
This document was last revised or approved by the OASIS Service Component Architecture / Bindings (SCA-Bindings) TC on the above date. The level of approval is also listed above. Check the Latest Version or Latest Approved Version location noted above for possible later revisions of this document.
Technical Committee members should send comments on this specification to the Technical Committees email list. Others should send comments to the Technical Committee by using the Send A Comment button on the Technical Committees web page at HYPERLINK "http://www.oasis-open.org/committees/sca-bindings/"http://www.oasis-open.org/committees/sca-bindings/.
For information on whether any patents have been disclosed that may be essential to implementing this specification, and any offers of patent licensing terms, please refer to the Intellectual Property Rights section of the Technical Committee web page (HYPERLINK "http://www.oasis-open.org/committees/sca-bindings/ipr.php"http://www.oasis-open.org/committees/sca-bindings/ipr.php.
The non-normative errata page for this specification is located at HYPERLINK "http://www.oasis-open.org/committees/sca-bindings/"http://www.oasis-open.org/committees/sca-bindings/.
Notices
Copyright OASIS 2007, 2008. All Rights Reserved.
All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website.
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, except as needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be followed) or as required to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.
This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
OASIS requests that any OASIS Party or any other party that believes it has patent claims that would necessarily be infringed by implementations of this OASIS Committee Specification or OASIS Standard, to notify OASIS TC Administrator and provide an indication of its willingness to grant patent licenses to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification.
OASIS invites any party to contact the OASIS TC Administrator if it is aware of a claim of ownership of any patent claims that would necessarily be infringed by implementations of this specification by a patent holder that is not willing to provide a license to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification. OASIS may include such claims on its website, but disclaims any obligation to do so.
OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS' procedures with respect to rights in any document or deliverable produced by an OASIS Technical Committee can be found on the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this OASIS Committee Specification or OASIS Standard, can be obtained from the OASIS TC Administrator. OASIS makes no representation that any information or list of intellectual property rights will at any time be complete, or that any claims in such list are, in fact, Essential Claims.
The names "OASIS", MACROBUTTON NoMacro [insert specific trademarked names and abbreviations here] are trademarks of OASIS, the owner and developer of this specification, and should be used only to refer to the organization and its official outputs. OASIS welcomes reference to, and implementation and use of, specifications, while reserving the right to enforce its marks against misleading uses. Please see HYPERLINK "http://www.oasis-open.org/who/trademark.php" http://www.oasis-open.org/who/trademark.php for above guidance.
Table of Contents
TOC \o "1-3" \h \z \u HYPERLINK \l "_Toc210621781" 1 Introduction PAGEREF _Toc210621781 \h 5
HYPERLINK \l "_Toc210621782" 1.1 Terminology PAGEREF _Toc210621782 \h 5
HYPERLINK \l "_Toc210621783" 1.2 Normative References PAGEREF _Toc210621783 \h 5
HYPERLINK \l "_Toc210621784" 1.3 Non-Normative References PAGEREF _Toc210621784 \h 5
HYPERLINK \l "_Toc210621785" 2 Operation Selection and Data Binding PAGEREF _Toc210621785 \h 6
HYPERLINK \l "_Toc210621786" 3 JCA Binding PAGEREF _Toc210621786 \h 7
HYPERLINK \l "_Toc210621787" 4 Binding Properties PAGEREF _Toc210621787 \h 10
HYPERLINK \l "_Toc210621788" 5 Additional Binding Configuration Data PAGEREF _Toc210621788 \h 12
HYPERLINK \l "_Toc210621789" 6 Examples PAGEREF _Toc210621789 \h 13
HYPERLINK \l "_Toc210621790" 6.1 Minimal JCA Binding PAGEREF _Toc210621790 \h 13
HYPERLINK \l "_Toc210621791" 6.2 Existing resources PAGEREF _Toc210621791 \h 13
HYPERLINK \l "_Toc210621792" 6.3 Resource Creation PAGEREF _Toc210621792 \h 13
HYPERLINK \l "_Toc210621793" 6.4 Existing Resources specified in the definition file PAGEREF _Toc210621793 \h 14
HYPERLINK \l "_Toc210621794" 7 Conformance PAGEREF _Toc210621794 \h 15
HYPERLINK \l "_Toc210621795" A. JCA Binding Schema PAGEREF _Toc210621795 \h 16
HYPERLINK \l "_Toc210621796" B. Java EE Connector Architecture PAGEREF _Toc210621796 \h 20
HYPERLINK \l "_Toc210621797" B.1 Introduction PAGEREF _Toc210621797 \h 20
HYPERLINK \l "_Toc210621798" B.2 Selected JCA CCI Interfaces PAGEREF _Toc210621798 \h 20
HYPERLINK \l "_Toc210621799" C. Acknowledgements PAGEREF _Toc210621799 \h 22
HYPERLINK \l "_Toc210621800" D. Non-Normative Text PAGEREF _Toc210621800 \h 23
HYPERLINK \l "_Toc210621801" E. Revision History PAGEREF _Toc210621801 \h 24
Introduction
This document presents bindings describing access and connectivity to the services provided by the Enterprise Information System (EIS).
This version of the document describes JCA Bindings thus narrowing connectivity down to the connectivity to the EIS system external to the SCA system, based on the J2EE Connector Architecture specification and implemented in Java.
Further specification is necessary to define EIS Bindings between different SCA runtimes within SCA system, for example J2EE and EIS based runtimes.
The JCA Bindings are applicable to the composites references and services.
The connection to exchange data with the EIS is characterized by two sets of configuration parameters, the connection and interaction parameters. The former set determines the location of the target system the latter determines characteristics that need to be specified to invoke one specific service available at the endpoint. JCA Binding model captures these parameters as separate sets to allow their reuse and reconfiguration.
Terminology
The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this document are to be interpreted as described in [ HYPERLINK \l "rfc2119" RFC2119]
Normative References
[RFC2119] S. Bradner, Key words for use in RFCs to Indicate Requirement Levels, HYPERLINK "http://www.ietf.org/rfc/rfc2119.txt" http://www.ietf.org/rfc/rfc2119.txt, IETF RFC 2119, March 1997.
[JCA15] Java Connector Architecture Specification Version 1.5HYPERLINK "http://java.sun.com/j2ee/connector/"http://java.sun.com/j2ee/connector/
[WSDL] E. Christensen et al, Web Service Description Language (WSDL) 1.1, HYPERLINK "http://www.w3.org/TR/2001/NOTE-wsdl-20010315" http://www.w3.org/TR/2001/NOTE-wsdl-20010315, W3C Note, March 15 2001.
R. Chinnici et al, Web Service Description Language (WSDL) Version 2.0 Part 1: Core Language, HYPERLINK "http://www.w3.org/TR/2007/REC-wsdl20-20070626/" http://www.w3.org/TR/2007/REC-wsdl20-20070626/, W3C Recommendation, June 26 2007.
Non-Normative References
TBD TBD
Operation Selection and Data Binding
The operation selection is a process used to identify the operation of the service that should be invoked.
The data binding is a process of data conversion between EIS and runtime formats.
This specification does not define default behavior for the operation selection nor data binding. This choice had been made because the interfaces describing data exchanged between JCA adapter and its client are specific to a particular adapter and, unlike JMS, cannot be used in a generic manner.
The JCA Binding implementation however, MUST use or provide the operation selection and data binding functionality. To support multiple adapters in a generic fashion, the binding MUST expose a mechanism for selecting or specifying the implementations of data bindings or operation selector. This protocol MUST be followed by this functionality providers. This can be achieved in a variety of ways, for example by providing the metadata information or specific pluggability points. This document does not specify such mechanism, it is left to the binding implementation.
JCA Binding
The JCA binding element is defined by the following schema:
*
Container|Application?
?
*
?
*
?
*
?
*
?
*
?
?
*
?
The binding.jca element has the following attributes:
/binding.jca/@uri the bindings uri attribute allows for the specification of the endpoint. For the reference, it defines the endpoint allowing connecting to the target EIS by providing JNDI name under which the ConnectionFactory is located. For the service, the uri defines the endpoint to allow the EIS system to connect to the SCA system by defining the JNDI lookup name of the ActivationSpec, for example uri=java:comp/env/eis/TRAN_EIS. The the bindings uri attribute is mutually exclusive with the connectionInfo element as well as jca.inbound.connection or jca.outbound.connection elements
/binding.jca/@connectionInfo identifies the jca.binding element present in the definitions document and whose child or children (one or more of jca.inbound.connection, jca.outbound.connection, jca.inbound.interaction, jca.outbound.interaction) are used to define characteristics of connection and interaction characteristics for this binding.
/binding.jca/@initialContextFactory the name of the JNDI initial context factory.
/binding.jca/@jndiURL the URL for the JNDI provider.
/binding.jca/@name - as defined in the SCA Assembly specification in Section 9, Binding
/binding.jca/@requires - as defined in the SCA Assembly specification in Section 9, Binding
/binding.jca/jca.outbound.connection defines the outbound connection characteristics, MUST NOT be specified for services
/binding.jca/jca.outbound.connection/@managed attribute that determines whether the interaction with the EIS system should be performed in the managed or non-managed mode. If the value is true (default), the JNDI name is used to obtain connection to the EIS and use adapter in the managed mode. If the value is false, the connection information is used to invoke adapter in the non-managed mode i.e. by creating instance of the ManagedConnectionFactory and using it to create Connection. For the full description of the managed and non-managed mode refer to section 6.9 of [JCA15]
/binding.jca/jca.outbound.connection/resourceAdapter specifies name, type and properties of the Resource Adapter Java bean. There may be a restriction, depending on the deployment platform, about specifying properties of the RA Java Bean. This element is only valid in the managed mode.
/binding.jca/jca.outbound.connection/resourceAdapter/@type the fully qualified name of the class implementing the JCA ResourceAdapter interface
/binding.jca/jca.outbound.connection/resourceAdapter/@name the optional name that uniquely identifies the existing instance of the resource adapter.
/binding.jca/jca.outbound.connection/resourceAdapter/property element contains the subset of the properties of the Resource Adapter Java Bean that need to be set in order to access specified EIS service. The full list of Resource Adapter properties can be obtained by introspecting the Java Bean.
/binding.jca/jca.outbound.connection/connection element specifies the properties of the connection factory used to create connections to the required service endpoint.
/binding.jca/jca.outbound.connection/connection/@type the fully qualified name of the class implementing the JCA ManagedConnectionFactory interface
/binding.jca/jca.outbound.connection/connection/@name if the create attribute is never, the name uniquely identifies existing instance of the managed connection factory. If create attribute is always, the name MUST be unique within domain.
/binding.jca/jca.outbound.connection/connection/property element contains the subset of the properties of the Managed Connectoin Factory Java Bean that need to be set in order to access specified EIS service. The full list of Managed Connectoin Factory properties can be obtained by introspecting the Java Bean.
/binding.jca/jca.outbound.connection/connection/@create attribute indicates whether the element containing the attribute should be created when the containing composite is deployed. Valid values are always, never and ifnotexist. The default value is ifnotexist. It is an error if the attribute value is always and the element with the given name already exists.
/binding.jca/jca.outbound.connection/connection/resAuth element specifies the authentication mechanism used by the resource adapter in the managed environment
Vendor specific extensions allow to customize the model to support the specific runtime characteristics, for example pool size or maximum number of connections
/binding.jca/jca.outbound.interaction defines characteristics of the outbound interaction, MUST NOT be specified for the services
/binding.jca/jca.outbound.interaction/connectionSpec identifies the name of the class implementing javax.resource.cci.ConnectionSpec interface and the set of connectionSpec properties to be specified when creating a connection, a client level connection properties e.g. user name or password. The ConnectionSpec object is used in several patterns that justify its definition in the interaction binding.
/binding.jca/jca.outbound.interaction/interactionSpec type specifies the name of the class implementing javax.resource.cci.InteractionSpec interface. The interaction specified outside of all operation applies to all the operations defined
/binding.jca/jca.outbound.interaction/operation element gathers characteristics of one operation of the service, the data bindings of the inbound and outbound arguments as well as interaction type and the properties.
/binding.jca/jca.inbound.connection defines the inbound connection characteristics, MUST NOT be specified for the references
/binding.jca/jca.inbound.connection/resourceAdapter specifies name, type and properties of the Resource Adapter Java bean. There may be a restriction, depending on the deployment platform, about specifying properties of the RA Java Bean. This element is only valid in the managed mode.
/binding.jca/jca.inbound.connection/resourceAdapter@type the fully qualified name of the class implementing the ResourceAdapter interface
/binding.jca/jca.inbound.connection/resourceAdapter/@name the optional name that uniquely identifies the existing instance of the resource adapter.
/binding.jca/jca.inbound.connection/activationSpec element specifies the name of the class implementing javax.resource.spi.ActivationSpec interface and its properties.
/binding.jca/jca.inbound.connection/activationSpec/@type the fully qualified name of the class implementing the ActivationSpec interface
/binding.jca/jca.inbound.connection/activationSpec/@name if the create attribute is never, the name uniquely identifies existing instance of the activation spec. If create attribute is always, the name MUST be unique within domain.
/binding.jca/jca.inbound.connection/activationSpec/@create attribute indicates whether the element containing the attribute should be created when the containing composite is deployed. Valid values are always, never and ifnotexist. The default value is ifnotexist. It is an error if the attribute value is always and the element with the given name already exists.
/binding.jca/jca.inbound.interaction defines characteristics of the inbound interaction, MUST NOT be specified for the references
/binding.jca/jca.inbound.interaction/listener type specifies the listener interface supported by this group of interactions. If the listener is not specified, it is assumed to be a istener implementing javax.resource.cci.MessageListener interface from the JCA specification
/binding.jca/jca.inbound.interaction/inboundOperation element maps the name of the EIS event received by ResourceAdapter to the name of the operation of the Service.
Extensibility - the JCA Bindings provide an extensibility mechanism that allows further customization of the bindings with the vendor specific attributes or elements using extensibility element in the schema as follows:
Binding Properties
The JCA Binding may contain properties necessary to interact with the EIS system, properties that are, however, not related to the service location or type of services available. Such properties SHOULD be configurable but SHOULD NOT require overwriting connection or interaction elements. Examples of such properties are user ID or password.
The binding.jca contains connectionInfo element that specifies the name of the binding.jca element in the definition file.
This element may contain the interaction properties, for example properties of the connectionSpec.
GROUP1
SYSAD
SYSAD
In the example above, the connectionSpec element specifies all the properties it overwrites in place and needs to be updated when there is a need to modify any of the properties. This could be inefficient at times and the method of passing properties from the bindings is defined. To get the value from the bindings, the property specifies the source attribute as follows.
GROUP1
SYSAD
The property value is the specified in the binding element that refers to the element in the definitions file.
SYSAD
The properties can also be specified by the composite, in that case the reference or service would contain the source attribute pointing to the property of the composite:
SYSAD
The indirection level of the binding, required even if the property value is specified in the composite prevents introducing hidden dependencies between the composite and definitions file.
Additional Binding Configuration Data
SCA runtime implementations may provide additional configuration that is associated with a JCA Binding, for example to overwrite binding properties like user name or password. The specification of such configuration is SCA runtime-specific and is outside of the scope of this document.
Examples
Minimal JCA Binding
The minimal JCA Binding only contains the bindings uri attribute with JNDI name of the connection factory. It allows to obtain the Connection to execute request against EIS using adapter. Since no interaction properties are specified, it is assumed that Resource Adapter accepts the null values for the invocation methods.
Existing resources
The sample reference with the JCA Binding, the bindings uri attribute specifies the existing resource - the JNDI name under which the connection factory object is located. The interaction properties are specified explicitly in the inlined jca.outbound.interaction element.
SYSAD
temp
read
Resource Creation
The following sample presents the reference with JCA bindings where the connection resources do not exist and need to be created.
D
localhost
C
Existing Resources specified in the definition file
This sample shows the resources specified in the definitions file and referred to by the binding elements. The definitions file contains the following
D
temp
C
The service with the JCA Bindings uses the connectionInfo attribute to identify the resources in the definition file
MyInboundListener
Conformance
Any SCA runtime that claims to support this binding MUST abide by the requirements of this specification.
The XML schema available at the namespace URI, defined by this specification, is considered to be authoritative and takes precedence over the XML Schema defined in the appendix of this document.
Within this specification, the following conformance targets are used:
XML document elements and attributes, including binding.jms and its children, and bindingType
The SCA runtime this refers to the implementation that provides the functionality to support the SCA specifications, including that specific to the JCA binding as well as other SCA capabilities
JCA objects, including ConnectionFactories and ActivationSpecs
WSDL documents
JCA Binding Schema
Java EE Connector Architecture
Introduction
The connector architecture specification defines set of contracts that allow interoperability of the resource adapters and application server environments. The specification also defines set of client interfaces that can be optionally supported by the adapter and allow the use of adapter functionality by the application clients. The following figure illustrates the relationships of these interfaces.
The SPI defines the following management contracts that give adapter consistent view of the infrastructure provided by the server and give sever consistent view of all the adapters thus helping with integration of adapters and servers.
Lifecycle management allows application server to control the startup of the adapter and notification to allow it to shutdown in an orderly fashion
Work management allows the adapter to use the server resources such as threads in an efficient way and allows server to manage system resources appropriately.
Connection management lets the server control the pooling, reusing and caching of the physical connections to the EIS system thus allowing for better scalability.
Transactions allow the server to control EIS resource managers and provide application clients with the transactional access to external resources.
Security contract allow for secure access to the EIS systems with security information configured and provided by the application server
Message inflow contract allows Resource Adapter to deliver events initiated by the EIS system to the application component executing on the application server.
Transaction inflow contract allow the application server to participate and execute in the context of the transaction initiated by the EIS system.
The CCI defines set of interfaces to access EIS functionality, through the resource adapter, from the application client. The CCI also provides access to some of the SPIs for transactions and security management to allow for executions of clients running in the non-managed mode, without the presence of the Application Server.
Selected JCA CCI Interfaces
Record
public interface javax.resource.cci.Record
extends java.lang.Cloneable, java.io.Serializable {
public String getRecordName(); public void setRecordName(String name);
public void setRecordShortDescription(String description);
public String getRecordShortDescription();
public boolean equals(Object other);
public int hashCode();
public Object clone() throws CloneNotSupportedException;
}
Interaction
public interface javax.resource.cci.Interaction {
public Connection getConnection();
public void close() throws ResourceException;
public boolean execute(InteractionSpec ispec,
Record input, Record output) throws ResourceException;
public Record execute(InteractionSpec ispec,
Record input) throws ResourceException;
}
MessageListener
interface javax.resource.cci.MessageListener {
Record onMessage(Record inputData) throws ResourceException;
}
Acknowledgements
The following individuals have participated in the creation of this specification and are gratefully acknowledged:
Participants: MACROBUTTON
MACROBUTTON NoMacro [Participant Name, Affiliation | Individual Member]
MACROBUTTON NoMacro [Participant Name, Affiliation | Individual Member]
Non-Normative Text
Revision History
MACROBUTTON NoMacro [optional; should not be included in OASIS Standards]
RevisionDateEditorChanges Made12008-01-16Anish KarmarkarApplied the OASIS template + related changes to the Submission22008-08-06Piotr PrzybylskiUpdates for consistency with JMS Binding and to resolve the following:
BINDING-13
BINDING-14
BINDING-28
BINDING-30
BINDING-32
BINDING-38
sca-jcabinding-1.1-spec-cd01 07 August 2008
Copyright OASIS 2007, 2008. All Rights Reserved. Page PAGE 4 of NUMPAGES 24
MACROBUTTON NoMacro [document identifier] MACROBUTTON NoMacro [specification date]
Copyright OASIS Open 2007, 2008.All Rights Reserved. Page PAGE 1 of NUMPAGES 25
G Y Z [ ] d e f @ A B C Q S T `
c
e
f
g
ۿᰦۍtn
h 0J $jj
hJHt hR B*Uph
hN 0J $j hJHt hR B*Uph
h 0J j h 0J U
h 0J hJHt hR 0J $j hJHt hR B*Uph hR hR 0J
hR 0J j hR 0J Uh h hN j hN U ( G Z k B
@
(
- gd gdSL gd C
G H I > ? @ A M
(
)
f
ڸԸԥڜږԸԃڜ}tmg_ j hN U
hN 0J hd hd hSL hd 0J
h 0J $j h h B*Uph
h 0J h h 0J $j4
h h B*Uph h h 0J $j) h h B*Uph
h 0J j h 0J UhSL hSL 5hN hSL hSL hSL hSL 0J %f
g
h
- C p q ] ^ _ X Y &