Re: [sca-bindings] Groups - sca-binding-jca-1.1-spec-cd02-issue63.docuploaded

Bryan,

I'm OK with the first two updates, however
with respect to the @uri and @connectionInfo/connection elements, the spec
in section 5 includes an example binding.jca element:

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

         
               connectionInfo="JCA_Services">

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

  </binding.jca>

So either the exclusivity statement
is incorrect or this example is incorrect.

Piotr, could you take a look at this?

Regards, Simon

Simon Holdsworth

STSM, SCA Bindings Architect; Master Inventor; OASIS SCA Bindings TC Chair

MP 211, IBM UK Labs, Hursley Park, Winchester SO21 2JN, UK

Tel +44-1962-815059 (Internal 245059) Fax +44-1962-816898

Internet - 

Bryan Aupperle <>

24/04/2009 19:33

To



cc

Subject

Re: [sca-bindings] Groups - sca-binding-jca-1.1-spec-cd02-issue63.doc
uploaded

I looked at this again (after looking at the prior version) and I had misread
a couple of things. 

BCJ20002 should remain but the attribute mentioned in the statement needs
to be /@initialContextFactory not /@connectionInfo.

BJC20003 is needed and correct. 

BJC20001 is a bit confusing.  I suggest rewording as follows:

The @uri attribute, the @connectionInfo attribute and jca.inbound.connection
or jca.outbound.connection elements are all mutually exclusive and the
SCA runtime MUST raise an error if more than one is present in a binding.jca
element. 

Bryan Aupperle, Ph.D.

STSM, WebSphere Enterprise Platform Software Solution Architect

Research Triangle Park,  NC 

+1 919-254-7508 (T/L 444-7508)

Internet Address:  

Bryan Aupperle/Raleigh/IBM@IBMUS

04/24/2009 09:58 AM

To



cc

Subject

Re: [sca-bindings] Groups - sca-binding-jca-1.1-spec-cd02-issue63.doc
uploaded

Overall this looks good, but some comments on BJC20001, BJC20002 and BJC20003.

BJC20001 covers BJC20002 so BJC20002 should be removed.

BJC20001 should be expanded to cover BJC20003 and BJC20003 removed.

Piotr, before I propose new wording for BJC20001, the spec points out that
@uri is mutually exclusive with either @connectionInfo or a [inbound|outbound].connection
element.  It the separately states that @jndiURL should not be used
with @uri.  I take this to mean that @uri and @jndiURL are mutually
exclusive.  Are @jndiURL and either @connectionInfo or a [inbound|outbound].connection
element mutually exclusive?  What about @connectionInfo and a [inbound|outbound].connection
element? 

Separately, the conformance section should be restructured along the lines
that Anish is proposing for the WS binding spec. 

Bryan Aupperle, Ph.D.

STSM, WebSphere Enterprise Platform Software Solution Architect

Research Triangle Park,  NC 

+1 919-254-7508 (T/L 444-7508)

Internet Address:  



04/08/2009 05:31 AM

To



cc

Subject

[sca-bindings] Groups - sca-binding-jca-1.1-spec-cd02-issue63.doc
uploaded

The document named sca-binding-jca-1.1-spec-cd02-issue63.doc has been

submitted by Mr. Simon Holdsworth to the OASIS Service Component

Architecture / Bindings (SCA-Bindings) TC document repository.

Document Description:

View Document Details:

http://www.oasis-open.org/committees/document.php?document_id=31989

Download Document:  

http://www.oasis-open.org/committees/download.php/31989/sca-binding-jca-1.1-spec-cd02-issue63.doc

PLEASE NOTE:  If the above links do not work for you, your email application

may be breaking the link into two pieces.  You may be able to copy
and paste

the entire link address into the address field of your web browser.

-OASIS Open Administration

Unless stated otherwise above:

IBM United Kingdom Limited - Registered in England and Wales with number
741598. 

Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU