groovy-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul King (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (GROOVY-1200) include appropriate JSP 2.0/EL implicit variables in Groovlets
Date Tue, 25 Apr 2017 22:06:04 GMT

     [ https://issues.apache.org/jira/browse/GROOVY-1200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Paul King closed GROOVY-1200.
-----------------------------
       Resolution: Implemented
         Assignee: Paul King
    Fix Version/s: 1.0

I am going to close this since all the big ticket items were covered a long time ago and as
Yazad's analysis shows, the other items aren't high priority. I suggest we let user demand
through new tickets drive any further work in this space.

> 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
>            Assignee: Paul King
>              Labels: contrib
>             Fix For: 1.0
>
>
> 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)

Mime
View raw message