Mailing-List: contact user-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Users List" <user@commons.apache.org>
Received-SPF: pass (nike.apache.org: domain of ralph.goers@dslextreme.com
 designates 209.85.132.244 as permitted sender)
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
Mime-Version: 1.0 (Apple Message framework v1075.2)
Subject: Re: [Configuration]JEXL question
From: Ralph Goers <ralph.goers@dslextreme.com>
In-Reply-To: <4A997354.2090704@gmx.de>
Date: Sat, 29 Aug 2009 13:10:17 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <78CB4600-96ED-46FB-9492-0D63895CC633@dslextreme.com>
References: <4A8A5F40.7020203@gmx.de>
 <D075690F-6AA2-46A8-AF0E-94795DB77BA3@dslextreme.com>
 <4A992E18.9050209@gmx.de>
 <E7C43D14-9932-4F76-B59F-75ADBE39957C@dslextreme.com>
 <C64424F0-2D42-417B-AB4D-F90CD7ED4075@dslextreme.com>
 <4A997354.2090704@gmx.de>
To: "Commons Users List" <user@commons.apache.org>

Sure, by all means.

Ralph

On Aug 29, 2009, at 11:28 AM, rzo wrote:

> Ralph,
>
> thanks for the fast reply.
> In the mean time i decided to try it with groovy.
> I have written a groovy expression interpolation which I will be  
> using in my project.
> If you are interested in this i could put the files on jira.
>
> - Ron
>
>
> Ralph Goers wrote:
>>
>> On Aug 29, 2009, at 10:35 AM, Ralph Goers wrote:
>>
>>>
>>> On Aug 29, 2009, at 6:33 AM, rzo wrote:
>>>
>>>> Hello,
>>>>
>>>> thanks for mentioning jexl scripting.
>>>> I tried it out and have found the following issue:
>>>>
>>>> evaluating the following:
>>>>
>>>> test=${expr:if (System.getProperty("user.home").startsWith("C"))  
>>>> {"x";} else {"z";}}
>>>>
>>>> does not seem to work.
>>>> Debuging shows that the expression forwarded to jexl is:
>>>>
>>>> if (System.getProperty("user.home").startsWith("C")) {"x";
>>>>
>>>> is this a bug ? or is there a way to escape the brackets within $ 
>>>> {...} ?
>>>>
>>>
>>> The "bug" is actually the way  
>>> org.apache.commons.lang.text.StrSubstitutor works. It can  
>>> configured be with prefix and suffix characters - the defaults are  
>>> '{' and '}' and after finding the prefix it just searches for the  
>>> first occurance of the suffix character - unless it finds a  
>>> recursive variable. So the string passed to  
>>> ConfigurationInterpolator is what you show above.
>>>
>>> However, it might be possible to override the suffix matcher to  
>>> look for an escape character.
>>>
>>
>> It occurs to me though that just using a different suffix matcher  
>> will not remove the escape character.
>>
>> One other thought. StrSubstitutor allows the prefix and suffix  
>> characters to be replaced, so you should be able to do
>>
>> conf.getSubstitutor().setVariablePrefix('`');
>> conf.getSubstitutor().setVariablesuffix('`');
>>
>> and then use test="$`expr:if (System.getProperty 
>> ("user.home").startsWith("C")) {"x";} else {"z";}`
>>
>> It also supports using strings so you could do:
>>
>> conf.getSubstitutor.setVariableSuffix("$}";
>>
>> and then test="${expr:if (System.getProperty("user.home").startsWith 
>> ("C")) {"x";} else {"z";}$}
>>
>> Of course, then you would have to use those prefix and suffix  
>> characters throughout that configuration.
>>
>> Ralph
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
>> For additional commands, e-mail: user-help@commons.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
> For additional commands, e-mail: user-help@commons.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@commons.apache.org
For additional commands, e-mail: user-help@commons.apache.org