> > Vitor Souza wrote:
> > > However, if you'd like I could create a JIRA
> (Bugzilla?) issue [...]
> > >
> > Yes, please create the ticket. Unfortunately, I
> don't believe there is
> > anyone left who _does_ have enough knowledge of
> OGNL
> > to truely vet it :(
Here it goes: https://issue
> Well, since we have full access to OGNL, why can't we just make the
> changes we need? Patrick should be able to hook us up :)
Sounds cool.
For those who are interested, more info about OGNL could be found at
http://www.opensymphony.com/ognl/
rgds
Don Brown <[EMAIL PROTECTED]> wrote: tm
sounds ok to me. But are we going to take it out in 2.1.x ? I'd prefer not to.
rgds
Matt Raible <[EMAIL PROTECTED]> wrote: +1 for restoring "do*".
Matt
On 11/6/06, Don Brown wrote:
> tm jee wrote:
> > Hi Vitor,
> >
> > I think the do fallback was removed from webwork. Have a look at
> > http:
+1 for restoring "do*".
Matt
On 11/6/06, Don Brown <[EMAIL PROTECTED]> wrote:
tm jee wrote:
> Hi Vitor,
>
> I think the do fallback was removed from webwork. Have a look
at http://cwiki.apache.org/confluence/display/WW/Key+Changes+From+WebWork+2 for more of
the changes from webwork to struts2
tm jee wrote:
Hi Vitor,
I think the do fallback was removed from webwork. Have a look at
http://cwiki.apache.org/confluence/display/WW/Key+Changes+From+WebWork+2 for more of
the changes from webwork to struts2.
Yeah, I'm thinking we should put this back. Struts 2.0.x is about
compatibili
tm jee wrote:
Hi guys,
I think this option is mentioned before in Struts2 maling list (by Ted if not
mistaken). What do you guys think about us forking Ognl? Ognl is just too
important to WebWork/Struts2.
Thoughts? Good? Bad
Well, since we have full access to OGNL, why can't we just make
Hi guys,
I think this option is mentioned before in Struts2 maling list (by Ted if not
mistaken). What do you guys think about us forking Ognl? Ognl is just too
important to WebWork/Struts2.
Thoughts? Good? Bad?
rgds
Alexandru Popescu <[EMAIL PROTECTED]> wrote: On 11/6/06, Don Brown wrote:
Hi Vitor,
I think the do fallback was removed from webwork. Have a look at
http://cwiki.apache.org/confluence/display/WW/Key+Changes+From+WebWork+2 for
more of the changes from webwork to struts2.
> Or maybe I did something wrong and I'm totally embarassing myself right
> now.
No you are not.
On 11/6/06, Don Brown <[EMAIL PROTECTED]> wrote:
Vitor Souza wrote:
>> I'd love to have proper generics support in OGNL. If
>> you create an OGNL
>> patch, be sure to let the Struts dev list know so we
>> can ensure it gets in.
>> Don
>>
>
> Don,
>
> I hacked OnglRuntime until it worked, but I d
> Vitor Souza wrote:
> > However, if you'd like I could create a JIRA (Bugzilla?) issue [...]
> >
> Yes, please create the ticket. Unfortunately, I don't believe there is
> anyone left who _does_ have enough knowledge of OGNL
> to truely vet it :(
Ok. I will work on that. I will build a quick
Vitor Souza wrote:
I'd love to have proper generics support in OGNL. If
you create an OGNL
patch, be sure to let the Struts dev list know so we
can ensure it gets in.
Don
Don,
I hacked OnglRuntime until it worked, but I don't think I have enough knowledge
of OGNL and Generics to say t
> I'd love to have proper generics support in OGNL. If
> you create an OGNL
> patch, be sure to let the Struts dev list know so we
> can ensure it gets in.
> Don
Don,
I hacked OnglRuntime until it worked, but I don't think I have enough knowledge
of OGNL and Generics to say that it would work
I'd love to have proper generics support in OGNL. If you create an OGNL
patch, be sure to let the Struts dev list know so we can ensure it gets in.
Don
Vitor Souza wrote:
Just to complement the previous post, I quickly ported the application to
Struts2 (by the way, it was VERY easy to do it!
I think we can definitely say we will not be moving from OGNL for the
Struts 2.0.x series, and most likely not for the Struts 2.1.x series.
If we did try to move from OGNL for 2.1.x, it would probably still be
the default, with the ability to switch OGNL for another EL for
experimental purpose
AFAIK, other projects have moved from OGNL usage. I am not gonna
discuss if it is a good or bad decision, but in case we are gonna move
away from it the old apps with heavy usage of OGNL will become more
complex to be migrated. Unfortunately, I am not sure how we can find
out what WW users have us
Just to complement the previous post, I quickly ported the application to
Struts2 (by the way, it was VERY easy to do it!) and removed my OgnlRuntime
hack and it does cause the problem.
The log file is here:
http://labes.inf.ufes.br/~vitor/ww_ognl_issue/cookbook-struts.log
The source code (Ecl
Hello there,
Let's go straight to the question: will Struts2 continue to use OGNL as WebWork
used to? Does that mean that OGNL will continue to be developed?
Now to the long story... Sometime ago I posted a message at the OGNL forum.
Here's the link:
http://forums.opensymphony.com/thread.jspa?
17 matches
Mail list logo