commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Benedict <>
Subject Re: [JEXL 2.0] o.a.c.jexl or o.a.c.jexl2 ?
Date Tue, 17 Nov 2009 22:28:32 GMT
I don't think there is a silver-bullet answer, but o.a.c.jexl2
sensible if the architecture radically changes.

Struts 2 and Tapestry 5 have the # in their package structure. The
reason for this is so old and new versions can run together within the
same web app class loader. This makes sense for frameworks.

Do you think this is beneficial to your users?


On Tue, Nov 17, 2009 at 4:09 PM, Henrib <> wrote:
> One (non Maven related) question for the JEXL community:
> The (soon-to-be published) JEXL-2.0 RCx version comes with a lot of changes.
> The upper level API deprecates ExpressionFactory & ScriptFactory - replaced
> by JexlEngine -, Expression methods that used to throw exceptions
> (ParseException, Exception) throw unchecked exceptions and the inner level
> classes (o.a.c.{util,introspection,etc}) have to many changes to be listed.
> Upper level API code compatibility has been checked through Jelly and more
> recently through Commons Configuration; 1.1 behavior seems preserved enough
> for the switch to JEXL-2.0 to be one compilation away.
> However, with so many changes and not so many checks, it may be preferable
> to be on the safe side and put the whole JEXL-2.0 into
> org.apache.commons.jexl2; this would allow 1.1 dependant code to continue
> living its merry way (OSGi non withstanding) and let switchers decide when
> to actually perform the switch.
> We need your opinions and options; let us know.
> Cheers
> Henrib
> --
> View this message in context:
> Sent from the Commons - Dev mailing list archive at
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message