The following comment has been added to this issue:

     Author: Stan Zapryanov
    Created: Wed, 27 Aug 2003 1:15 PM
       Body:
After a little more research, I was able to correct the problem by setting a system 
property:

    //System.setProperty("ognl.keepLastEvaluation","true");
    System.setProperty("ognl.traceEvaluations","true");

---------------------------------------------------------------------
View the issue:

  http://jira.opensymphony.com/secure/ViewIssue.jspa?key=XW-82


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: XW-82
    Summary: Integration with newer OGNL releases
       Type: Bug

     Status: Assigned
   Priority: Minor

    Project: XWork
   Versions:
             1.0-beta1

   Assignee: Patrick Lightbody
   Reporter: Stan Zapryanov

    Created: Wed, 27 Aug 2003 11:45 AM
    Updated: Wed, 27 Aug 2003 11:45 AM
Environment: NT, JDK 1.4_3, and OGNL 2.6.x

Description:
It seems that some changes made to ONGL in its newer versions are causing a 
NullPointerException for ognlContext.getCurrentEvaluation().get..

Example in CompoundRootAccessor:

ognlContext.pushEvaluation(new 
Evaluation(ognlContext.getCurrentEvaluation().getNode(), o));

What I believe are the related changes made in OGNL 2.6.0:
(Full info under http://www.ognl.org/2.6.0/ReleaseNotes.html)

Ability to turn off evaluation tracing for speed reasons. This is an effect of 
reimplementing the way indexed access is done. Evaluation tracing overhead is about 2x 
slower than without so this can be very significant. 
Keep track of whether to store the last evaluation or release it (if tracing is on). 
The default is true (keep last evaluation) for compatibility but having your code that 
creates contexts default this to false is recommended if you want to keep memory usage 
down. These get created a lot and if you don't have a good reason to remember the last 
Evaluation after an expression is run then you should be letting them get recycled. An 
alternative (I know M?ns Klercker needs this) is to use the last Evaluation and then 
call OgnlContext.recycleLastEvaluation() to let it get back into the pool. 
OgnlException now stores the root evaluation that caused an exception. This is 
regardless of the setting of keepLastEvalution in the context (if tracing is on), but 
this will not occur unless the evaluation tracing is enabled. 



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.opensymphony.com/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork

Reply via email to