← Prev in month ← Prev in thread
Next in thread → Next in month →

ISSUE-168: Conversion rules for property values are not specified -proposal

From
David Booz <>
Date
2009-11-16T22:22:02+00:00
ID
Thread
ISSUE-168: Conversion rules for property values are not specified -proposal
Hi folks,

This should give you something to think about. Attached is a proposed resolution for Issue 168 [1].  As far as I can tell, there are two important points for us to consider.

When converting an XML property value to a JAXB annotated type:

(a) JAXB allows for validation of the XML to be on or off.  My proposal says validation must be on.  Remember we're talking about property values here, not messages between components.

(b) JAXB allows for custom bindings of XML schema to Java.  My proposal says that the runtime must use the default schema to Java binding.

See sections 2.1.5 and 4.2.2.  I'm not opposed to moving the 2.1.5 text to the @Property annotation section.

(See attached file: sca-javacaa-1.1-spec-cd03-rev1+Issue168.doc)

[1] http://www.osoa.org/jira/browse/JAVA-168

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:

sca-javacaa-1.1-spec-cd03-rev1+Issue168.doc
← Prev in month ← Prev in thread
Next in thread → Next in month →