geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Genender (JIRA)" <>
Subject [jira] Commented: (XBEAN-26) [RTC] Nested properties not evaluated for named constructor args
Date Tue, 01 Aug 2006 14:40:15 GMT
    [ ] 
Jeff Genender commented on XBEAN-26:

+1...but this looks more like a bug fix..IMHO, this does not require RTC...I would commit
and close.

> [RTC] Nested properties not evaluated for named constructor args
> ----------------------------------------------------------------
>                 Key: XBEAN-26
>                 URL:
>             Project: XBean
>          Issue Type: Bug
>          Components: spring
>            Reporter: Dain Sundstrom
>         Assigned To: Dain Sundstrom
>             Fix For: 2.6
>         Attachments: named-constructor-arg-fixes.patch
> Nested property elements are not evaluated when they are constructor arguments.  For
example the following three declarations should be equivalent:
> {code}
>   <s:soup id="soupService" type="French Onion"/>
>   <s:soup id="nestedBean">
>     <s:type>
>       <bean class="java.lang.String">
>         <constructor-arg index="0" value="French Onion"/>
>       </bean>
>     </s:type>
>   </s:soup>
>   <s:soup id="nestedValue">
>     <s:type>
>       <value>French Onion</value>
>     </s:type>
>   </s:soup>
> {code}
> The patch attempts to find a setter for the property and if not located assumes it is
type Object instead of just aborting the evaluation.  This means that constructor args without
a matching getter or setter can't support our custom map element code because we don't knot
the type of the constructor argument at this point in the code.  Fixing that will take a much
bigger restructure of the code.
> There are test cases included with the patch. Note there is one new file included with
the patch that must be svn added.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message