OF837CB56F.DDA48227-ON8525762C.0063BDE6-8525762C.0064518E@us.ibm.com"
type="cite">
Target: JCA binding specification
(CD03)
Description: BJC20008 and BJC20014
appear to contradict BJC20007 and BJC20013 respectively because
BJC20008
and BJC20014 are not clear that they are referring to JEE resources
that
may have been defined outside of an SCA Domain.
Proposal:
Reword the two statements:
The SCA runtime SHOULD raise an error
if the
connection/@create attribute value is “always”
and a resource with the given name already exists in the JEE node
[BJC20008].
The SCA runtime SHOULD raise an error
if the
activationSpec/@create attribute value is “always”
and a resource with the given name already exists in the JEE node
[BJC20014].
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: aupperle@us.ibm.com
----- Forwarded by
Bryan
Aupperle/Raleigh/IBM on 09/09/2009 02:09 PM -----
I've taken a pass at the TA document for the JCA
binding.
You can find them at [1,2]. Items to note:
1) JCA CD03 spec - line 138 and 186 - What does restrict mean?
2) JCA CD03 spec - lines 154-155 should probably be normative
3) To my untrained JCA eyes, BJC20007 and BJC20008 are contradictory?
Same
question for BJC20013 and BJC20014. If they are not contradictory, some
please explain it to me.
4) I have no idea what to specify for tags in each TA
5) Not sure that BJC-TA-20016 is even remotely close to correct
[1] http://www.oasis-open.org/committees/download.php/34108/sca-jcabinding-1.1-test-assertions-wd02.doc
[2] http://www.oasis-open.org/committees/download.php/34109/sca-jcabinding-1.1-test-assertions-wd02.pdf
Dave Booz
STSM, BPM and SCA Architecture
Co-Chair OASIS SCA-Policy TC and SCA-J TC
"Distributed objects first, then world hunger"
Poughkeepsie, NY (845)-435-6093 or 8-295-6093
e-mail:booz@us.ibm.com