The proposal doesn't say anything about typing. Was your assumption that the runtime would attempt to coerce the string values into the type of the property? If so;
1) you need to say how that works in the spec.
2) you need to describe what happens if the coercion fails.
If not, then you need to explicity state that the property type has to be string [] to use this feature.
Do you still think we need to do this?
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:
Simon Nash ---06/29/2009 06:10:32 AM---I am attaching updated JavaCAA and JavaCI documents containing a proposed resolution to JAVA-139.
From:
Simon Nash <>
To:
OASIS Java <>
Date:
06/29/2009 06:10 AM
Subject:
[sca-j] JAVA-139: Proposed resolution
I am attaching updated JavaCAA and JavaCI documents containing
a proposed resolution to JAVA-139.
Simon
[attachment "sca-javacaa-1.1-spec-cd03+issue139.doc" deleted by David Booz/Poughkeepsie/IBM] [attachment "sca-javaci-1.1-spec-cd01+issue139.doc" deleted by David Booz/Poughkeepsie/IBM] ---------------------------------------------------------------------
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
