It's a dependency, not a requirement, to be precise although I guess you meant
that. To create a stripped-down struts, I'd ditch OGNL and do the conversion and
formatting with some other way. Bear in mind, OGNL is used all over for other
stuff too, but I did say I'd also ditch that.
Bob Tiernay on 21/03/08 15:56, wrote:
Really??? I didn't realize OGNL was a requirement for tags to perform
conversion and formatting.
--------------------------------------------------
From: "James Mitchell" <[EMAIL PROTECTED]>
Sent: Friday, March 21, 2008 9:58 AM
To: "Struts Developers List" <dev@struts.apache.org>
Subject: Re: If I had 1000 hours to give...
No it doesn't, but then neither does the Struts tags if "no OGNL" :)
On Fri, Mar 21, 2008 at 9:45 AM, Adam Hardy <
[EMAIL PROTECTED]> wrote:
Really??? I don't think jsp:getProperty does conversion and formatting -
does it?
James Mitchell on 20/03/08 16:49, wrote:
> Actually, and not trying to be funny here, but ... that's available
today...
>
> <jsp:getProperty name="myBean" property="foo"/>
>
> http://java.sun.com/products/jsp/tags/11/tags11.html
>
>
>
> On Thu, Mar 20, 2008 at 11:42 AM, Adam Hardy <
> [EMAIL PROTECTED]> wrote:
>
>> +1
>>
>> in fact, i'd write a new taglibrary with just lightweight support for
form
>> properties, conversion, and formatting. No HTML, no Ajax, no OGNL, no
>> value stack.
>>
>> Then I'd do a session of performance testing to see what the
improvement
>> was
>> (did somebody else suggest that?).
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
