aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rex Wang (JIRA)" <>
Subject [jira] [Commented] (ARIES-727) support syntax : ${a+b} in blueprint-cm
Date Thu, 01 Sep 2011 03:35:09 GMT


Rex Wang commented on ARIES-727:

At revision: 1163525, add unit test for this feature.
At revision: 1163899, make the commons-jexl a optional dependency. People won't need this
if he don't use the syntax ${a+b} in blueprint-ext.
This still commit to 0.3 branch.

Hi, Jeremy, Thanks for the information! I did not notice that and assumed trunk is at 0.4.x
level... I will port all the changes to trunk soon :-)


> support syntax : ${a+b} in blueprint-cm 
> ----------------------------------------
>                 Key: ARIES-727
>                 URL:
>             Project: Aries
>          Issue Type: New Feature
>          Components: Blueprint
>    Affects Versions: blueprint-0.3.1, blueprint-0.4.0
>            Reporter: Rex Wang
>            Assignee: Rex Wang
>             Fix For: blueprint-0.4.0
>         Attachments: ARIES-727-blueprint-cm.patch, ARIES-727-fixes-in-blueprint-ext.patch
> I am wondering if Aries blueprint-cm support such scenario:
> <cm:property-placeholder id="property-placeholder" persistent-id="" placeholder-prefix="${"
>         <cm:default-properties>
>             <cm:property name="port" value="12345"/>
>             <cm:property name="offset" value="10"/>
>         </cm:default-properties>
> </cm:property-placeholder>
> <xxx:conn name="loc" uri="http://localhost:${port+offset}"/>
> I have a test, but seems the ${port+offset} can not be replaced with value "12355".
> -Rex
> -----------------------
> Hi Rex,
> to my knowledge (substantiated with a quick code inspection) the placeholders in Aries
today support no operators or arithmetic like that. But please do raise an Improvement JIRA
for the future :)
> Regards,
> Valentin
> -----------------------
> When we support this, we need to perform a 'plus' or string concatenate
> operation based on the variable type:).
> Therefore. when specifying the property in the blueprint xml, the explicit
> type should be specified if not string.
> Regards,
> Emily
> -----------------------
> I _think_ I wrote something like this for xbean-blueprint since it didn't look like blueprint
supported it.  IIRC I used the same calculation engine as the geronimo config substitutions.
 I think you can infer what kind of calculation to do (addition or concatenation) from the
type of the property you end up setting.
> thanks
> david jencks

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message