[
https://issues.apache.org/jira/browse/TUSCANY-3184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755451#action_12755451
]
Ramkumar Ramalingam commented on TUSCANY-3184:
----------------------------------------------
Hi Jennifer,
I agree that, the SCA Spring Specs v1.0 does not provide a clear picture on
whether the properties
can deal with primitive types. I believe the SCA Spring Specs 1.1 will address
this issue.
In reality, the SCA properties does not support the direct use of primitive
types like int, short, boolean etc.
The SCA properties are designed to deal with JAXB data types, which always
points to a class
implementation.
For example: SCA property for integer should point to java.lang.Integer class.
> Spring <sca:property> tags must point to classes, primitives are not permitted
> ------------------------------------------------------------------------------
>
> Key: TUSCANY-3184
> URL: https://issues.apache.org/jira/browse/TUSCANY-3184
> Project: Tuscany
> Issue Type: Improvement
> Components: Java SCA Spring Implementation Extension
> Affects Versions: Java-SCA-1.5
> Environment: WebSphere Application Server
> Reporter: Jennifer A Thompson
> Assignee: Ramkumar Ramalingam
> Fix For: Java-SCA-1.5.1
>
>
> Since the Spring <sca:property> tag is a bean (per spec) it must point to a
> class implementation. I can imagine situations where a customer would prefer
> to point to a primitive type, such as int, short, boolean, etc. Since the
> spec explitily mentions that the sca:property creates a bean, this may need
> to be addressed at spec level.
> Also, since constructor-args can use primitive types, if a user doesn't
> specify explicit spring -> sca mapping tags, is it possible to create
> primitive type sca properties via this mechanism?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
