Closed jfut closed 9 years ago
Flexibility of Lasta Di's JavaScript expression is less than OGNL. so the pattern is unsupported for now.
While, Lasta Di suggests you keep Di xml to be simple as possible. (do not use complex expression)
But if you need the pattern, I will try to resolve it. Give me a time to think about implementation.
Or you can switch the engine to your original OGNL engine by 'dixml.script.expression.engine' in lasta_di.properties. (that implements ExpressionEngine interface)
thanks.
[share] target class is JavaScriptExpressionEngine in Lasta Di.
You can define it at the next version 0.6.4 (deployed 0.6.4-A-SNAPSHOT for now) The test case is following:
<component name="sea" class="org.docksidestage.mylasta.trial.TrialDiSea"/>
<component name="land" class="org.docksidestage.mylasta.trial.TrialDiLand"/>
<component name="parks">[sea, land]</component>
<component name="maihama" class="org.docksidestage.mylasta.trial.TrialDiMaihama">
<property name="parkList">parks</property>
</component>
However simple cases are only supported, sorry... e.g. o [sea, land] x [sea, land, [iks, bonvo], amba] // has nested list
We try to improve incrementally, so your feedback is very glad to us. Thank you.
Fixed class is: SimpleExpressionPlainHook
It sounds good! Thanks for improvement.:smile:
test.xml:
I get the following error:
Is this expression mistaken?