Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (nike.apache.org: domain of paulus.benedictus@gmail.com
 designates 209.85.223.187 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type;
        b=jCufmn9Gk7VLDZV09IRF6X5ICFqa4qS3rj2FxtLKEjF0CW/kW4TQFDFK7D1WNECdUn
         t2nVz2zekY98jyD13WSXuk0xPv/ALYZSiJoWcMqwDD/SUYUDVENIC1bYoLm/nET8BtSn
         JpVCUPewTkKJdAmiIDwvbCuUYUz5OW+aIqOEI=
MIME-Version: 1.0
Sender: paulus.benedictus@gmail.com
In-Reply-To: <26396881.post@talk.nabble.com>
References: <26396881.post@talk.nabble.com>
Date: Tue, 17 Nov 2009 16:28:32 -0600
Message-ID: <b9e663070911171428x3e2baf9fv47931083cd36c85d@mail.gmail.com>
Subject: Re: [JEXL 2.0] o.a.c.jexl or o.a.c.jexl2 ?
From: Paul Benedict <pbenedict@apache.org>
To: Commons Developers List <dev@commons.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

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?

Paul

On Tue, Nov 17, 2009 at 4:09 PM, Henrib <hbiestro@gmail.com> 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: http://old.nabble.com/-JEXL-2.0--o.a.c.jexl-or-o.a.c.jexl2---tp26396881p26396881.html
> Sent from the Commons - Dev mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>

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