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

[David Booz <booz@us.ibm.com>]

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

Simon 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