Carsten Ziegeler wrote:
Reinhard Poetz wrote:
Carsten Ziegeler wrote:
Reinhard Poetz work:
Currently we use the xreporter artifact from
http://people.apache.org/repo/m1-snapshot-repository/xreporter/jars/xreporter-expression-r683.jar
in cocoon-forms.
After getting the Avalon and Excalibur artifacts published to the central Maven
repo, this this is, AFAICS the last dependency not being available from Maven
central.
As we are approaching a cocoon-forms release candiate, I would like to see this
dependency available from there and getting rid of our use of
http://people.apache.org/repo/m1-snapshot-repository which isn't meant to
contain releases.
Dump question (and I'm not against using the xreporter stuff, I'm really
just curious), do we need the xreporter stuff? Isn't it doing similar
stuff which we also have inside the jxtg?
I think that we don't have something in our codebase that could replace the
xreporter stuff in a *backwards-compatible* way, have we?
Not sure about all features of the xreporter expression stuff, but we
have expression stuff in the jxtg which perhaps covers all use cases and
just needs a simple addition to handle everything in a compatible way. I
don't know, that's why I ask :)
Carsten
I have never understood why a new expression language has been
introduced. Why don't we simply use Rhino for expression evaluation?
JXTG already does that (apart from jexl and jxpath).
What jexl and jxpath are missing is probably some basic support for
control statements (if) that XReporter has built in. As 'if' in
XReporter is actually implemented as a function we could fairly easy
mimic this behaviour in jexl.
The biggest problem would be incompatible syntax.
--
Leszek Gawron http://www.mobilebox.pl/krs.html
CTO at MobileBox Ltd.
