Mailing-List: contact dev-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Struts Developers List" <dev@struts.apache.org>
Received-SPF: pass (hermes.apache.org: domain of schneidh@gmail.com designates
 64.233.166.181 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding;
        b=I7NrgwL2DwsV/f2o+vuNLgXGAqAqzDG0bRk6gVsXOoIpFusQ2r8Q8pYMj87BzAHzJlUZKv42F9KHus/rXKluWYW0VZc4fvwC0SPIb4TAEyEXRbuNpCa1x1s/psFxXz2k8QMEcw+7m3uDlr3UigsL7qXjl532Vh1GnrPabcvit8Q=
Message-ID: <4599EB46.5070002@gmail.com>
Date: Mon, 01 Jan 2007 23:19:02 -0600
From: Tom Schneider <schneidh@gmail.com>
User-Agent: Thunderbird 1.5.0.9 (X11/20061206)
MIME-Version: 1.0
To: Struts Developers List <dev@struts.apache.org>
Subject: Re: OGNL performance detrimental to Struts 2
References: <7825136.post@talk.nabble.com>
 <a74683f90612111658tfea9371t1b82ccd8e145255f@mail.gmail.com>
 <7847866.post@talk.nabble.com> <457FCC12.9030905@fdar.com>
 <8b3ce3790612130431v3ab6d87cn61c6f80c7a2ddf14@mail.gmail.com>
 <7865392.post@talk.nabble.com> <4580EBC4.7030101@twdata.org>
 <1c661f2f0612171914sbd1f27bnef4cfbff1bbffcfb@mail.gmail.com>
 <7933372.post@talk.nabble.com> <7940372.post@talk.nabble.com>
 <4587492C.9060605@twdata.org> <7940484.post@talk.nabble.com>
 <45874BC9.4010109@twdata.org> <7940543.post@talk.nabble.com>
In-Reply-To: <7940543.post@talk.nabble.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Tonight I was looking at abstracting away OGNL from xwork.  (I was 
pretty far before I gave up for the night, about a half dozen OGNL 
references in xwork that I'll have to look at a little closer)  So I 
took a look at what it would take to integrate MVEL.  First, the lack of 
javadoc is a little disappointing.  (There wasn't a single line of 
javadoc comment that I could find)  Secondly, the integration guide 
isn't very extensive, just some basic examples.  Based on these 2 items 
alone, it may not be as trivial as advertised to figure out how to 
integrate MVEL into XWork.  On the other hand OGNL is not without it's 
issues. :)

I'll probably look at it a bit later when I'm farther with xwork, but 
that's my take on it thus far for what it's worth.
Tom

Chris Brock wrote:
> Don't dare me.  I'm pretty ambitious.  I wrote MVEL 1.0 in three days.
>
>
> Don Brown-2 wrote:
>   
>> I'd like it to be possible for a Struts developer to swap in a new EL, 
>> perhaps MVEL, if they didn't like OGNL for some reason.  If you can 
>> create a patch to make that happen, I would consider it my early 
>> Christmas present :)
>>
>> Don
>>
>> Chris Brock wrote:
>>     
>>> Why do you think it would be so terribly difficult?  What does MVEL not
>>> support that is currently supported by OGNL that would not be fixable by
>>> a
>>> few tweaks to MVEL's syntax?
>>>
>>> Generally, MVEL's API architecture follows the same pattern as OGNL,
>>> supports type coercion, conversion, projections, etc.  
>>>
>>> Not to mention that MVEL is now an active project and OGNL is not, and of
>>> course the performance advantage in MVEL which is only getting better by
>>> the
>>> day.
>>>
>>>
>>> Don Brown-2 wrote:
>>>   
>>>       
>>>> If you can find a way to completely replace OGNL by MVEL, I'd be very 
>>>> interested to see it. :)
>>>>
>>>> Don
>>>>
>>>>         


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