DO NOT REPLY [Bug 20034] New: - Invalid cache in InsertTag

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20034>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20034

Invalid cache in InsertTag

           Summary: Invalid cache in InsertTag
           Product: Struts
           Version: 1.1 Beta 2
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Critical
          Priority: Other
         Component: Tiles framework
        AssignedTo: struts-dev@jakarta.apache.org
        ReportedBy: tjung@classys.hu


Symptom: In some cases the cachedCurrentContext property of the InsertTag use 
the ComponentContext of the previous request. 

Explanation: If an error occured between the start and the end tag, the 
releaseInternal won't be invoked. If the application server uses tag handler 
pool (and it is) the next request will see the old ComponentContext with 
invalid attributes.

Solution: Our patched InsertTag calls releaseInternal in the release method:
   public void release() {

        super.release();
        attribute = null;
        beanName = null;
        beanProperty = null;
        beanScope = null;

        definitionName = null;
        flush = true;
        name = null;
        page = null;
        role = null;
        isErrorIgnored = false;
        //patch
        releaseInternal();
        //EO patch
    }

---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org