Service Component Architecture JCA Binding Specification Version 1.1

Committee Draft 01

7th August, 2008

Specification URIs:

This Version:

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.doc

http://docs.oasis-open.org/opencsa/sca-bindings/sca-jcabinding-1.1-spec-cd01.pdf (Authoritative)

Previous Version:

 

Latest Version:

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.doc

http://docs.oasis-open.org/opencsa/sca-bindings/sca-jcabinding-1.1-spec.pdf (Authoritative)

Latest Approved Version:

 

Technical Committee:

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 composite’s 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 Committee’s email list. Others should send comments to the Technical Committee by using the “Send A Comment” button on the Technical Committee’s web page at 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 (http://www.oasis-open.org/committees/sca-bindings/ipr.php.

The non-normative errata page for this specification is located at 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",  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 http://www.oasis-open.org/who/trademark.php for above guidance.

 

Table of Contents

1      Introduction. 5

1.1       Terminology. 5

1.2       Normative References. 5

1.3       Non-Normative References. 5

2      Operation Selection and Data Binding. 6

3      JCA Binding. 7

4      Binding Properties. 10

5      Additional Binding Configuration Data. 12

6      Examples. 13

6.1       Minimal JCA Binding. 13

6.2       Existing resources. 13

6.3       Resource Creation. 13

6.4       Existing Resources specified in the definition file. 14

7      Conformance. 15

A.     JCA Binding Schema. 16

B.     Java EE Connector Architecture. 17

B.1 Introduction. 17

B.2 Selected JCA CCI Interfaces. 17

C.     Acknowledgements. 17

D.     Non-Normative Text 17

E.     Revision History. 17

 

 

1       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 composite’s 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.

1.1      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 [RFC2119]

1.2      Normative References

[RFC2119]              S. Bradner, Key words for use in RFCs to Indicate Requirement Levels, http://www.ietf.org/rfc/rfc2119.txt, IETF RFC 2119, March 1997.

[JCA15]                  Java Connector Architecture Specification Version 1.5
http://java.sun.com/j2ee/connector/

[WSDL]                  E. Christensen et al, Web Service Description Language (WSDL) 1.1, 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, http://www.w3.org/TR/2007/REC-wsdl20-20070626/, W3C Recommendation, June 26 2007.

1.3       Non-Normative References

TBD                       TBD

2       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.

 

 

 

3       JCA Binding

The JCA binding element is defined by the following schema:

<binding.jca connectionInfo="QName"?

             initialContextFactory=”xs:anyURI”?

             jndiURL=”xs:anyURI”?

             name=”NCName”?

             requires=”listofQName”?

             uri=”xsd:anyURI”?>

     

      <jca.outbound.connection managed="xs:boolean" ?>

            <resourceAdapter name=”NMTOKEN” type="NMTOKEN”>

                  <property name=“NMTOKEN” type=“NMTOKEN”>*

            </resourceAdapter>?

            <connection name=”NMTOKEN”? type="NMTOKEN” create=”string”?>

                  <property name=“NMTOKEN” type=“NMTOKEN”>*

            </connection>

            <resAuth>Container|Application</resAuth>?

            <!-- Vendor specific extensions -->

      </jca.outbound.connection>?

      <jca.inbound.connection>

            <resourceAdapter name=”NMTOKEN”? type="NMTOKEN”>

                  <property name=“NMTOKEN” type=“NMTOKEN”>*

            </resourceAdapter>

            <activationSpec name=”NMTOKEN”? type="NMTOKEN” create=”string”?>

                  <property name=“NMTOKEN” type=“NMTOKEN”>*

            </activationSpec>

                  <!-- Vendor specific extensions -->

      </jca.inbound.connection>?

     

      <jca.outbound.interaction>

            <connectionSpec type=”NMTOKEN”>

                  <property name=“NMTOKEN” type=“NMTOKEN”>*

            </connectionSpec>?

            <interactionSpec type=”NMTOKEN”>

                  <property name=“NMTOKEN” type=“NMTOKEN”>*

            </interactionSpec>?

            <operation name="NMTOKEN">

                  <interactionSpec type=”NMTOKEN”?>

                        <property name=”NMTOKEN” type=”NMTOKEN”>*

                  </interactionSpec>?

            </operation>*

                  <!-- Vendor specific extensions -->

      </jca.outbound.interaction>?

      <jca.inbound.interaction>

            <listener type=”NMTOKEN” />?

            <inboundOperation name="NMTOKEN" nativeOperation="NMTOKEN">*

            </inboundOperation>

      </jca.inbound.interaction>?

</binding.jca>

 

The binding.jca element has the following attributes:

 

·        /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”

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:

4       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.

 

   <reference name="EISHelloWorldReference">

         <binding.jca uri=" java:comp/env/eis/EISMCF"

                        connectionInfo="JCA_Services">

         </binding.jca>

   </reference>

 

This element may contain the interaction properties, for example properties of the connectionSpec.

   <definitions targetNamespace="http://acme.com"

                xmlns="http://docs.oasis-pen.org/ns/opencsa/sca/200712">

         <binding.jca name="JCA_Services">

                <jca.outbound.interaction >

                       <connectionSpec name="FAConnectionSpec">

                             <property name="group">GROUP1</property>

                             <property name="userid">SYSAD</property>

                             <property name="password">SYSAD</property>

                       </connectionSpec>

                       …

                </jca.outbound.interaction>

         </binding.jca>

   </definitions>

 

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. 

 

         <jca.outbound.interaction >

                <connectionSpec

                        name="connector.file.outbound.FAConnectionSpec">

                       <property name="group">GROUP1</property>

                       <property name="userid">SYSAD</property>

                       <property name="password" source="$password"/>

                </connectionSpec>

         </jca.outbound.interaction>

 

The property value is the specified in the binding element that refers to the element in the definitions file.

 

   <reference name="JCAHelloWorldReference">

         <binding.jca uri=" java:comp/env/eis/MCF "

                        connectionInfo="JCA_Services">

                <property name=”password”>SYSAD</property>    

         </binding.jca>

   </reference>

 

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:

 

<composite xmlns="http://docs.oasis-pen.org/ns/opencsa/sca/200712

           name="EISHelloworld">

 

     <reference name="EISHelloWorldReference">

   <binding.jca uri=" java:comp/env/eis/EISMCF"

                 connectionInfo="JCA_Services">

                <property name=”userid” source=”$UID”/>

   </binding.jca>

   </reference>

 

 

   <property name=”UID”>SYSAD</property>

</composite>

 

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.

5       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.

6       Examples

6.1      Minimal JCA Binding

The minimal JCA Binding only contains the binding’s 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.

 

 

   <!-- JCA reference, connection is configured in JNDI context -->

   <reference name="EISHelloWorldReference">

         <binding.jca uri="java:comp/env/eis/EISMCF"/>

   </reference>

 

6.2      Existing resources

The sample reference with the JCA Binding, the binding’s 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.

 

   <reference name="EISHelloWorldReference">

         <binding.jca uri="java:comp/env/eis/EISMCF">

                <jca.outbound.interaction>

 

                       <connectionSpec name="FAConnectionSpec">

                             <property name="userid">SYSAD</property>

                       </connectionSpec>

                       <interactionSpec name="FAInteractionSpec">

                       </interactionSpec>

 

                       <operation name="hello">

                             <interactionSpec>

                                    <property name="dir">temp</property>

                                    <property name="fileMode">read</property>

                             </interactionSpec>

                       </operation>

 

                </jca.outbound.interaction>

         </binding.jca>

   </reference>

 

6.3      Resource Creation

The following sample presents the reference with JCA bindings where the connection resources do not exist and need to be created.

   <reference name="JCAHelloWorldReference">

         <binding.jca>

                <jca.outbound.connection managed="true">

                       <resourceAdapter

                             name="connector.file.FAResourceAdapter">

                             <property name="logDrive">D</property>

                       </resourceAdapter>

                       <connection name="FAManagedConnectionFactory"

                             create="always">

                             <property name="host">localhost</property>

                             <property name="drive">C</property>

                       </connection>

                </jca.outbound.connection>

         </binding.jca>

   </reference>

 

6.4      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

<definitions targetNamespace="http://acme.com"

             xmlns="http://docs.oasis-pen.org/ns/opencsa/sca/200712">

 

   <binding.jca name="JCA_Inbound">

         <jca.inbound.connection>

                <resourceAdapter name="FAResourceAdapter">

                       <property name="logDrive">D</property>

                </resourceAdapter>

                <activationSpec     name="FAActivationSpec">

                       <property name="directory_type">temp</property>

                       <property name="drive">C</property>

                </activationSpec>

         </jca.inbound.connection>

   </binding.jca>

</definitions>

 

The service with the JCA Bindings uses the connectionInfo attribute to identify the resources in the definition file

<service name="JCAHelloWorldService">

   <binding.jca connectionInfo=" JCA_Inbound ">

         <jca.inbound.interaction>

                <listener>MyInboundListener</listener>

                <inboundOperation name="hello" nativeOperation="TXPN"/>                             <inboundOperation name="bye" nativeOperation="ETXPRN"/>

         </jca.inbound.interaction>

   </binding.jca>

</service>

 

7       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

A.   JCA Binding Schema

 

<?xml version="1.0" encoding="UTF-8"?>

<!-- (c) Copyright OASIS 2007, 2008 -->

<schema xmlns="http://www.w3.org/2001/XMLSchema"     

      targetNamespace=" http://docs.oasis-open.org/ns/opencsa/sca/200712"

      xmlns:sca=" http://docs.oasis-open.org/ns/opencsa/sca/200712"       elementFormDefault="qualified">

      <include schemaLocation="sca-core.xsd" />

      <complexType name="JCABinding">

      <complexContent>

      <extension base="sca:Binding">

            <sequence>

            <element name="jca.outbound.connection"                    

                        type="sca:JCAOutboundConnection"

                                    minOccurs="0" />

            <element name="jca.inbound.connection"

                        type="sca:JCAInboundConnection"

                              minOccurs="0" />

            <element name="jca.outbound.interaction"

                        type="sca:JCAOutboundInteraction"

                                    minOccurs="0" />

            <element name="jca.inbound.interaction"

                        type="sca:JCAInboundInteraction"

                                    minOccurs="0" />

            <element name="property" type="sca:Property" minOccurs="0"

                                    maxOccurs="unbounded" />

            <any namespace="##other" processContents="lax" minOccurs="0"

                                    maxOccurs="unbounded" />

            </sequence>

            <attribute name="connectionInfo" type="anyURI" use="optional" />

            <attribute name="initialContextFactory"

                        type="anyURI" use="optional"/>

            <attribute name="jndiURL" type="anyURI" use="optional"/>

            <anyAttribute namespace="##any" processContents="lax" />

      </extension>

      </complexContent>

      </complexType>

      <simpleType name="CreateResource">

            <restriction base="string">

                  <enumeration value="always" />

                  <enumeration value="never" />

                  <enumeration value="ifnotexist" />

            </restriction>

      </simpleType>

      <simpleType name="ResAuth">

            <restriction base="string">

                  <enumeration value="Container" />

                  <enumeration value="Application" />

            </restriction>

      </simpleType>

      <complexType name="JCAOutboundConnection">

            <sequence>

                  <element name="resourceAdapter" type="sca:ResourceAdapter"

                        minOccurs="0" />

                  <element name="connection" type="sca:Connection" />

                  <element name="resAuth" type="sca:ResAuth" minOccurs="0" />

                  <any namespace="##other"

                        processContents="lax" minOccurs="0"

                        maxOccurs="unbounded" />

            </sequence>

            <attribute name="managed" type="boolean" use="optional"

                  default="true" />

            <anyAttribute namespace="##any" processContents="lax" />

      </complexType>

      <complexType name="JCAInboundConnection">

            <sequence>

            <element name="resourceAdapter" type="sca:ResourceAdapter" />

            <element name="activationSpec" type="sca:ActivationSpec" />

            <any namespace="##other" processContents="lax" minOccurs="0"

                        maxOccurs="unbounded" />

            </sequence>

      </complexType>

      <complexType name="JCAOutboundInteraction">

            <sequence>

            <element name="connectionSpec" type="sca:ConnectionSpec"

                        minOccurs="0" />

            <element name="interactionSpec" type="sca:InteractionSpec"

                        minOccurs="0" />

            <element name="operation" type="sca:Operation" minOccurs="0" />

            <any namespace="##other" processContents="lax" minOccurs="0"

                        maxOccurs="unbounded" />

            </sequence>

      </complexType>

      <complexType name="JCAInboundInteraction">

            <sequence>

            <element name="listener" type="string" minOccurs="0" />

            <element name="inboundOperation" type="sca:InboundOperation"

                        minOccurs="0" maxOccurs="unbounded" />

            <any namespace="##other" processContents="lax" minOccurs="0"

                        maxOccurs="unbounded" />

            </sequence>

      </complexType>

      <complexType name="ResourceAdapter">

            <sequence>

            <element name="property" type="sca:Property" minOccurs="0"

                        maxOccurs="unbounded" />

            <any namespace="##other" processContents="lax" minOccurs="0"

                        maxOccurs="unbounded" />

            </sequence>

            <attribute name="name" type="NMTOKEN" use="optional" />

            <attribute name="type" type="NMTOKEN" use="required" />

            <anyAttribute namespace="##any" processContents="lax" />

      </complexType>

      <complexType name="Connection">

            <sequence>

            <element name="property" type="sca:Property" minOccurs="0"

                        maxOccurs="unbounded" />

            <any namespace="##other" processContents="lax" minOccurs="0"

                        maxOccurs="unbounded" />

            </sequence>

            <attribute name="name" type="NMTOKEN" use="optional" />

            <attribute name="type" type="NMTOKEN" use="required" />

            <attribute name="create" type="sca:CreateResource" use="optional"

                  default="ifnotexist" />

            <anyAttribute namespace="##any" processContents="lax" />

      </complexType>

      <complexType name="ActivationSpec">

            <sequence>

            <element name="property" type="sca:Property" minOccurs="0"

                        maxOccurs="unbounded" />

            <any namespace="##other" processContents="lax" minOccurs="0"

                        maxOccurs="unbounded" />

            </sequence>

            <attribute name="name" type="NMTOKEN" use="optional" />

            <attribute name="type" type="NMTOKEN" use="required" />

            <attribute name="create" type="sca:CreateResource" use="optional"

                  default="ifnotexist" />

            <anyAttribute namespace="##any" processContents="lax" />

      </complexType>

      <complexType name="Operation">

            <sequence>

            <element name="interactionSpec" type="sca:InteractionSpec"

                        minOccurs="0" />

            <any namespace="##other" processContents="lax" minOccurs="0"

                        maxOccurs="unbounded" />

            </sequence>

            <attribute name="name" type="NMTOKEN" use="required" />

            <anyAttribute namespace="##any" processContents="lax" />

      </complexType>

      <complexType name="InboundOperation">

            <sequence>

            <any namespace="##other" processContents="lax" minOccurs="0"

                        maxOccurs="unbounded" />

            </sequence>

            <attribute name="name" type="NMTOKEN" use="required" />

            <attribute name="nativeOperation" type="string" use="required" />

            <anyAttribute namespace="##any" processContents="lax" />

      </complexType>

      <complexType name="ConnectionSpec">

            <sequence>

            <element name="property" type="sca:Property" minOccurs="0"

                        maxOccurs="unbounded" />

            <any namespace="##other" processContents="lax" minOccurs="0"

                        maxOccurs="unbounded" />

            </sequence>

            <attribute name="type" type="NMTOKEN" use="required" />

            <anyAttribute namespace="##any" processContents="lax" />

      </complexType>

      <complexType name="InteractionSpec">

            <sequence>

            <element name="property" type="sca:Property" minOccurs="0"

                        maxOccurs="unbounded" />

            <any namespace="##other" processContents="lax" minOccurs="0"

                        maxOccurs="unbounded" />

            </sequence>

            <attribute name="type" type="NMTOKEN" use="required" />

            <anyAttribute namespace="##any" processContents="lax" />

      </complexType>

      <element name="binding.jca" type="sca:JCABinding"

            substitutionGroup="sca:binding" />

</schema>

B.   Java EE Connector Architecture

B.1 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

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.

B.2 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;

   }

 

 

C.  Acknowledgements

The following individuals have participated in the creation of this specification and are gratefully acknowledged:

Participants:

 

D.  Non-Normative Text

E.   Revision History

 

Revision

Date

Editor

Changes Made

1

2008-01-16

Anish Karmarkar

Applied the OASIS template + related changes to the Submission

2

2008-08-06

Piotr Przybylski

Updates for consistency with JMS Binding and to resolve the following:

BINDING-13

BINDING-14

BINDING-28

BINDING-30

BINDING-32

BINDING-38