tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 22566] New: - Allow RequestContext (or RequestCycle) to be accessed by OGNL in 'property-specifications'
Date Tue, 19 Aug 2003 19:36:22 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=22566>.
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=22566

Allow RequestContext (or RequestCycle) to be accessed by OGNL in 'property-specifications'

           Summary: Allow RequestContext (or RequestCycle) to be accessed by
                    OGNL in 'property-specifications'
           Product: Tapestry
           Version: 3.0
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Framework
        AssignedTo: tapestry-dev@jakarta.apache.org
        ReportedBy: colinml1@exis.com


<property-specification> blocks in page definitions are very useful to
declaratively add properties to a page. Unfortunately, due to the fact that
pages are constructed and _then_ attached, there is no way for an OGNL
expression in the property-specification to get at the RequestContext (and from
there, the ServletContext for example).

One workaround is to define a custom Engine class which stuffs the needed data
in the Global object, which _is_ available at the time property-specifications
are processed, but this solution is less than optimal in some cases.

I suggest that an enhancement be added such that the OGNL expression can get at
the current RequestContext and/or RequestCycle.

Mime
View raw message