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 37592] New: - VariableResolverImpl is ignorant of the implicit variables 'request' and 'response'
Date Tue, 22 Nov 2005 15:16:56 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=37592>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=37592

           Summary: VariableResolverImpl is ignorant of the implicit
                    variables 'request' and 'response'
           Product: Commons
           Version: Nightly Builds
          Platform: Other
               URL: http://cvs.apache.org/viewcvs.cgi/jakarta-
                    commons/el/src/java/org/apache/commons/el/VariableResolv
                    erImpl.java?rev=1.3&view=markup
        OS/Version: other
            Status: NEW
          Keywords: RFC, NeedsReleaseNote
          Severity: major
          Priority: P2
         Component: EL
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: db@dawnbreaks.net


I refer you to JSP.8.8 of the JSP 2.0 FR spec (and also of the JSP 2.1 draft),
where INSTEAD OF the implicit 'pageContext' object, there are meant to be
'request' and 'response' implicit objects.

This isn't working for me with tag files produced by some version of Jasper/EL
embedded in Sun Java System Application Server 8 (specifically, when I invoke a
function like '${f:myFunction(request)}' from a tag file, a null pointer is
passed to the function).  From a fairly quick read of the current source, it
would appear that the call-stack initiated by
org.apache.jasper.runtime.PageContextImpl.proprietaryEvaluate(...) ultimately
defers to org.apache.commons.el.VariableResolverImpl to discover implicit
objects used in an expression.

And VariableResolverImpl simply doesn't know about 'request' and 'response'. 
Notice also that -- when invoked in the context of a Tag file -- it  *shouldn't*
know about 'pageContext' either.

http://cvs.apache.org/viewcvs.cgi/jakarta-commons/el/src/java/org/apache/commons/el/VariableResolverImpl.java?rev=1.3&view=markup

As to whether the Jasper crowd are using Commons EL correctly or not, I'm not to
judge, but it does seem to me that the EL layer should get the heads up first.


have fun,
David.



My own keywords:  Jasper EL tag file tagfile implicit variable variables request
response pageContext NullPointerException JSP expression evaluate null

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
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