geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivan (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GERONIMO-6292) Share the japser servlet between jasper plugin and web-container plugin.
Date Thu, 01 Mar 2012 16:51:58 GMT

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

Ivan commented on GERONIMO-6292:
--------------------------------

Commit changes to 3.0-beta branch at rev.1295667.
Now, if users would like to turn on jsp debugging, two steps are required
a. set GERONIMO_OPTS=-Dorg.apache.geronimo.webapplication.stage=development
b. update the jasper-deployer in config.xml with :
<gbean name="JspModuleBuilderExtension">
            <attribute name="defaultJspServlet" propertyEditor="org.apache.geronimo.web25.deployment.utils.WebAppXmlAttributeBuilder">
                <web-app:web-app xmlns="http://java.sun.com/xml/ns/javaee" xmlns:web-app="http://java.sun.com/xml/ns/javaee">
                    <servlet>
                        <servlet-name>jsp</servlet-name>
                        <servlet-class>org.apache.jasper.servlet.JspServlet</servlet-class>
                        <init-param>
                            <param-name>development</param-name>
                            <param-value>true</param-value>
                     </init-param>
                        <init-param>
                            <param-name>trimSpaces</param-name>
                            <param-value>false</param-value>
                     </init-param>
                        <init-param>
                            <param-name>fork</param-name>
                            <param-value>false</param-value>
                     </init-param>
                        <init-param>
                            <param-name>logVerbosityLevel</param-name>
                            <param-value>DEBUG</param-value>
                     </init-param>
                        <init-param>
                            <param-name>xpoweredBy</param-name>
                            <param-value>false</param-value>
                     </init-param>
                        <init-param>
                            <param-name>engineOptionsClass</param-name>
                            <param-value>org.apache.geronimo.jasper.JspServletOptions</param-value>
                     </init-param>
                        <load-on-startup>0</load-on-startup>
                 </servlet>
                    <servlet-mapping>
                        <servlet-name>jsp</servlet-name>
                        <url-pattern>*.jsp</url-pattern>
                        <url-pattern>*.jspf</url-pattern>
                        <url-pattern>*.jspx</url-pattern>
                        <url-pattern>*.xsp</url-pattern>
                 </servlet-mapping>

            </web-app:web-app>
            </attribute>
        </gbean>

Still need to improve the steps, hopefully we only need to configure the first step to make
it work soon.
                
> Share the japser servlet between jasper plugin and web-container plugin.
> ------------------------------------------------------------------------
>
>                 Key: GERONIMO-6292
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-6292
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: web
>    Affects Versions: 3.0-beta-1
>            Reporter: Ivan
>             Fix For: 3.0, 3.0-beta-2
>
>
> Now, if users would like to turn on jsp debug, they may need to update config.xml in
two modules, one is jasper, and another is webcontainer deployer. Think that it is not user-friendly.
Think that it is better to have the jsp servlet configuration in the jasper plugin, and webcontainer
plugins could share it from there.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message