You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Dan Becker (JIRA)" <de...@tuscany.apache.org> on 2009/03/11 15:14:50 UTC

[jira] Assigned: (TUSCANY-2899) SCA 1.x failed to get the property value for the complex type when using @element

     [ https://issues.apache.org/jira/browse/TUSCANY-2899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Becker reassigned TUSCANY-2899:
-----------------------------------

    Assignee: Dan Becker

> SCA 1.x failed to get the property value for the complex type when using @element
> ---------------------------------------------------------------------------------
>
>                 Key: TUSCANY-2899
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-2899
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA Assembly Model
>    Affects Versions: Java-SCA-1.3.1
>            Reporter: Ku Jun Guo
>            Assignee: Dan Becker
>
> It's similiar to TUSCANY-2898, when I used the @element attribute for the property:
> <property name="complexType" element="test:globalElement1">
>             <test:globalElement1>
>             	<firstData>complex1</firstData>
>             	<secondData>complex2</secondData>
>             </test:globalElement1>
>  </property>
> I still failed to get the value for firstData and secondData, but in OSOA spec, such example is allowed:
> 1239 Declaration of a property with an element type:
> 1240 <property name="elementFoo" element="foo:fooElement">
> 1241 <foo:fooElement>
> 1242 <foo:a>AValue</foo:a>
> 1243 <foo:b>InterestingURI</foo:b>
> 1244 </foo:fooElement>
> 1245 </property>
> So it should be implemented in Tuscany SCA 1.1.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.