It's really an XWork question anyway. If anything like this were to
happen, it would need to happen at the XWork level (as did Guice, aka
com.opensymphony.xwork2.inject).
-Ted.
On 11/13/06, tm jee <[EMAIL PROTECTED]> wrote:
I see. At first I was thinking that if we have the source in struts2 c
I see. At first I was thinking that if we have the source in struts2 code base,
we could do a release of ognl with fixes whenever we release webwork. Ognl
development seems to be inactive for a long time. I think Pat have commit
access to Ognl code, but are we allow to do a release of Ognl when
On 11/13/06, tm jee <[EMAIL PROTECTED]> wrote:
Hey guys,
What do you guys think about moving Ognl code base into Struts2, just like
what was did with Guice?
I would not be in favour of that. As Don implies, that means that we would
effectively be forking OGNL and taking on the responsibility
What would be the advantage? I'm open to the idea, but need to be
convinced of the value. Guice was included because:
1. I didn't want the Guice classes interfering with Struts
applications, if they wanted to run a newer version of Guice
2. Guice is only a few classes
The problems with OGNL i
Hey guys,
What do you guys think about moving Ognl code base into Struts2, just like what
was did with Guice?
rgds
-
All new Yahoo! Mail "The new Interface is stunning in its simplicity and ease
of use." - PC Magazine
