[jira] [Commented] (GROOVY-1200) include appropriate JSP 2.0/EL implicit variables in Groovlets

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (GROOVY-1200) include appropriate JSP 2.0/EL implicit variables in Groovlets

JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/GROOVY-1200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15975960#comment-15975960 ]

Paul King commented on GROOVY-1200:
-----------------------------------

This issue is quite old. Before commencing, it would be worth doing a gap analysis between what is currently available[1] and what might be expected within vanilla JSP code[2].

[1] http://docs.groovy-lang.org/latest/html/api/groovy/servlet/ServletBinding.html
[2] http://docs.oracle.com/javaee/1.4/tutorial/doc/JSPIntro7.html#wp71043

> include appropriate JSP 2.0/EL implicit variables in Groovlets
> --------------------------------------------------------------
>
>                 Key: GROOVY-1200
>                 URL: https://issues.apache.org/jira/browse/GROOVY-1200
>             Project: Groovy
>          Issue Type: New Feature
>          Components: Groovlet / GSP
>    Affects Versions: 1.0-JSR-4
>            Reporter: Demis Bellot
>              Labels: contrib
>
> While we're making life easier for the developer we should also add familiar JSP 2.0/el objects where appropriate.
> looking at: http://java.sun.com/j2ee/1.4/docs/tutorial/doc/JSPIntro7.html, we see these variables
>     * param: Maps a request parameter name to a single value
>     * paramValues: Maps a request parameter name to an array of values
>     * header: Maps a request header name to a single value
>     * headerValues: Maps a request header name to an array of values
>     * cookie: Maps a cookie name to a single cookie
>     * initParam: Maps a context initialization parameter name to a single value
> Finally, there are objects that allow access to the various scoped variables described in Using Scope Objects.
>     * pageScope: Maps page-scoped variable names to their values
>     * requestScope: Maps request-scoped variable names to their values
>     * sessionScope: Maps session-scoped variable names to their values
>     * applicationScope: Maps application-scoped variable names to their values
> Out of these i think it makes sense to have:
> param,paramValues,header,headerValues,cookie,requestScope,sessionScope,applicationScope



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)