ndpoint if we could get
> something like this going.
> Tom
>
> Jessek wrote:
>> I don't know how relevant it is to the conversation or how awful it's
>> going
>> to be trying to do it but I did plan on taking a stab at creating a new
>> unified-el compat
I don't know how relevant it is to the conversation or how awful it's going
to be trying to do it but I did plan on taking a stab at creating a new
unified-el compatible grammar for OGNL when I do my big IoC-friendly
re-factor. (probably a 2.7.3 release kind of change)
Since jboss and others alr
Hah, I knew it must've been Struts.
Congrats on joining the project Matt, I'm sure you'll have fun doing it.
(or at least be more in control of your own destiny)
p.s. sorry the message is so many days off from the original post..
--
View this message in context:
http://www.nabble.com/New-
I don't see it listed at http://wiki.opensymphony.com/dashboard.action.
I also don't know who Rainer is - but if someone sets up the right perms or
an OGNL space I'll be happy to import the OGNL page that is currently
sitting in the struts2 apache wiki.
Philip Luppens wrote:
>
> Jesse, just a
I've got a first pass attempt at documenting some of the kinds of things
anyone attempting to use the new OGNL 2.7 compilation features will need to
know completed:
http://cwiki.apache.org/confluence/display/WW/OGNL+Expression+Compilation
I'm not sure where these conversations should take place
ontinue to use OGNL, do we want to look into migrating OGNL to the
> ASF?
>
> -Ted.
>
> On 7/14/07, Jessek <[EMAIL PROTECTED]> wrote:
>>
>> I was wondering if anyone here might be able to create an OGNL wiki space
>> in
>> http://wiki.opensymphony.com fo
I was wondering if anyone here might be able to create an OGNL wiki space in
http://wiki.opensymphony.com for me. Username is jkuhnert there I think.
If nothing can be done there I was thinking of just adding a new page to
http://cwiki.apache.org/confluence/display/WW/Home - but am a little fe
Probably a little early to say for sure, but I don't think anyone needs to
worry about ognl performance anymore. I'm sure the right people will update
everyone when the time is right.
husted wrote:
>
> Did you try using the simple theme with Struts 2.0.1 in the benchmarks?
>
> -Ted.
>
> On 1
I'm not sure what you mean by "property accessor". The Tapestry community is
just as tied down/used to using ognl expressions as much as any other.
Tapestry-prop is a side project Howard created for very specific consulting
engagements where the performance overhead of ognl was unacceptable for so
I'm still not getting all of the hand wringing that is going on in this
thread about ognl. There is what I think a perfectly reasonable solution
that will help finish up those last remaining bits that ognl needs to really
be production ready.
Despite whatever we want to call it you could theoret
;d still be open to doing whatever I can to help, even if it means taking
some direction in design suggestions from others.
Bob Lee wrote:
>
> I wouldn't jump straight to a bytecode solution, there's no reason it
> should
> be that much faster than a well-designed plain Java solu
Last time I'll interrupt your normal dev cycle I promise.
Since it seems we are both equally screwed in the short term by any non ognl
solution it might be beneficial to consider just fixing it. I'm very
familiar with javassist bytecode manipulation and vaguely familiar with the
internal working
You may want to take a peek at the svn source tree in t5. It has a slightly
better version of these semantics. (though I doubt you'll find any advanced
sort of expr support like ognl might provde)
That being said, 1ms or so is all it takes to render a lot of tapestry
pages, so I wouldn't discount
Would you guys be "morally offended" if I lifted this code? (or potentially
did, need to see how amenable the two are first, but it shouldn't be too
hard)
I mean, I know licensing is blah blah and all , but you know...Maybe it's
not "right".
Bob Lee wrote:
>
>
> In the mean time, we wrote a
14 matches
Mail list logo
