commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 20534] New: - context variable not accessible from threads
Date Fri, 06 Jun 2003 00:43:37 GMT
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=20534>.
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=20534

context variable not accessible from threads

           Summary: context variable not accessible from threads
           Product: Commons
           Version: Nightly Builds
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Jelly
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: billk@tech.beacon-it.co.jp


Inside of a <threads:thread> you cannot access the context variable.  For 
example, ${context.findVariable(foo)} doesn't work.

Fix is in JellyContext.java.  But I can't checkin the fix because I don't have 
access to CVS (and no one has answered my mails to the jakarta-commons list).
The problem is that the setVariables() call erases the "context" variable set 
in the init() call.  One possible fix is:

    public void setVariables(Map variables) {
       this.variables = variables;
        variables.put("context", this);
    }

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


Mime
View raw message