[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: ISSUE 168: Conversion rules for property values are not specified - updatedproposal
On the last telecon, the following points were raised:
1) Would llike non-normative text stating that other databindings are possible when JAXB is not explicitly used. Text was added to both J-CAA and J-POJO specs.
2) Does JAXB and SDO map Java primitives types the same way? Yes they do. This has not changed in the latest SDO3 specs under development. Note: the 'char' primitive is an interesting one in that neither SDO nor JAXB are capable of mapping it round trip by default. Both need help from schema annotations to make it work. This means that if Java char is used as the type of a Java @Property, the property type in the component definition will have to point to a schema that has either the JAXB or SDO annotations in it (and possibly some custom code as well). However, once you've done that you are either using JAXB annotations or not and so I think we're covered in the spec with what's already there. This is tricky so comments are welcome.
3) Add clause about JAXB annotations in the Java type of an unannotated SCA property in the J-POJO spec.
(See attached file: sca-javacaa-1.1-spec-cd03-rev1+Issue168_v3.doc)(See attached file: sca-javaci-1.1-spec-cd01-rev2_issue168v2.doc)
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
sca-javacaa-1.1-spec-cd03-rev1+Issue168_v3.doc
sca-javaci-1.1-spec-cd01-rev2_issue168v2.doc
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]