I have been using OGNL 2.7.2 with Struts 2.0.11.2 and 2.1.2 for a while
without any problems.  Maybe it's something in OGNL 2.7.3 that is
incompatible.
  (*Chris*)

On Thu, Oct 2, 2008 at 6:45 AM, Owen Berry <[EMAIL PROTECTED]> wrote:

> In light of this issue, it would be nice if a newer version of ognl
> could be used within struts. I'm using the 2.1.2 beta and it also
> depends on ognl-2.6.11. Not sure how simple it would be to update to a
> newer ognl though as struts-2.1.2 also depends on xwork-2.1.1, which
> depends on ognl-2.6.11, so it would need to be updated too.
>
> On Thu, Oct 2, 2008 at 7:41 AM,  <[EMAIL PROTECTED]> wrote:
> > Hi,
> > I can see that many of my threads stays blocked for a long time in
> gnl.OgnlRuntime.invokeMethod line 511.
> > If this is to any help.
> > :-)
> >
> >
> >> -----Ursprungligt meddelande-----
> >> Från: [EMAIL PROTECTED]
> >> [mailto:[EMAIL PROTECTED]
> >> Skickat: den 2 oktober 2008 12:11
> >> Till: user@struts.apache.org
> >> Ämne: Ognl versions
> >>
> >> Hi,
> >> We use struts2-core 2.0.11.2 which according to maven use
> >> opensymphony.ognl version 2.6.11.
> >>
> >> I wonder what the relationships is to ognl.ognl and
> >> specifically if the opensymphony version also has the bug
> >> http://jira.opensymphony.com/browse/OGNL-141
> >>
> >> When we are doing load tests we get very long response times.
> >> I tried to replace opensymphony.ognl version 2.6.11 with
> >> ognl.ognl version 2.7.3 but got functional errors.
> >>
> >> Regards
> >> Gunnar
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Reply via email to