Re: [sca-j] ISSUE-168: Conversion rules for property values are notspecified

[Simon Nash <oasis@cjnash.com>]

Dave,
The JavaCI mapping for property types is in the opposite direction
(Java->XML) from the mapping for property values (XML->Java).  Also,
the mapping for values is defined in a different part of the JAXB
spec (Appendix B: Unmarshaling) than the type mappings.

It may be reasonably obvious what is supposed to happen if the JAXB
XML->Java unmarshaling of the property value supplied in the component
definition is compatible with the Java type of the property, though
I still think it's worth being explicit.

It is not quite so obvious what is supposed to happen if the
property value supplied in the component definition isn't compatible
with the Java type of the property.  For example, is it required or
recommended that the SCA runtime detects such an error at deployment
time rather than deferring it until runtime?  If the error is
detected at runtime, how is it reported by the SCA runtime?  The
JAXB spec allows application-defined validation handlers to catch
and fix up such errors; is it required that all SCA runtimes
support these?

I'll answer your point about the "Java to Java" aspect of Issue 139
on the other thread.  Let's continue that discussion there.

   Simon

David Booz wrote:
> Hi Simon,
> 
> Referring to the other thread [1], I see now that you're focusing on the 
> XML to Java type coercion, and now I'm sure we're talking about 
> different aspects of the problem. I was focused on the Java to Java 
> aspect introduced by the proposal to Issue 139, and you've focused on on 
> the Component to implementation problem. Section 8 of the JCI spec does 
> describe the Java to componentType mapping as based on JAXB. Why doesn't 
> this address your concern?
> 
> [1] http://lists.oasis-open.org/archives/sca-j/200907/msg00005.html
> 
> 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
> 
> Inactive hide details for David Booz---07/02/2009 08:29:23 
> AM---http://www.osoa.org/jira/browse/JAVA-168 Dave BoozDavid 
> Booz---07/02/2009 08:29:23 AM---http://www.osoa.org/jira/browse/JAVA-168 
> Dave Booz
> 
> 
> From:	
> David Booz/Poughkeepsie/IBM@IBMUS
> 
> To:	
> sca-j@lists.oasis-open.org
> 
> Date:	
> 07/02/2009 08:29 AM
> 
> Subject:	
> [sca-j] ISSUE-168: Conversion rules for property values are not specified
> 
> ------------------------------------------------------------------------
> 
> 
> 
> _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:booz@us.ibm.com
> 
> Inactive hide details for Simon Nash ---07/02/2009 06:24:45 
> AM---Resending with "NEW ISSUE" tag in the email subject line. TARGSimon 
> Nash ---07/02/2009 06:24:45 AM---Resending with "NEW ISSUE" tag in the 
> email subject line. TARGET: Java Common Annotations and APIs
> 
> From:	
> Simon Nash <oasis@cjnash.com>
> 
> To:	
> OASIS Java <sca-j@lists.oasis-open.org>
> 
> Date:	
> 07/02/2009 06:24 AM
> 
> Subject:	
> [sca-j] NEW ISSUE: Conversion rules for property values are not specified
> 
> ------------------------------------------------------------------------
> 
> 
> 
> Resending with "NEW ISSUE" tag in the email subject line.
> 
> TARGET: Java Common Annotations and APIs
> 
> DESCRIPTION: Conversion rules for property values are not specified
> 
> The @Property annotation allows component implementations to
> define SCA properties of any Java type.  However, there are no
> rules stated for how property values specified in component
> definitions are converted to the Java type of the property,
> or what happens if this conversion fails.
> 
> PROPOSAL:
> 
> The conversion rules should follow the JAXB rules for mapping
> XML to Java.
> 
> Suitable text should be added to section 2.1.5 describing how
> property value conversions are performed and what happens if
> the conversion fails.
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:_
> __https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php_ 
> 
> 
> 
>