You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Yi Xiao (Commented) (JIRA)" <ji...@apache.org> on 2012/03/01 03:17:59 UTC
[jira] [Commented] (GERONIMODEVTOOLS-788) The hot deploy of jsp and
other static resource files do not work even under the development mode
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13219733#comment-13219733 ]
Yi Xiao commented on GERONIMODEVTOOLS-788:
------------------------------------------
Submitted at revision 1295380 and 1295382
> The hot deploy of jsp and other static resource files do not work even under the development mode
> -------------------------------------------------------------------------------------------------
>
> Key: GERONIMODEVTOOLS-788
> URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-788
> Project: Geronimo-Devtools
> Issue Type: Bug
> Components: eclipse-plugin
> Affects Versions: 3.0, 3.0-beta-1
> Reporter: Yi Xiao
> Assignee: Yi Xiao
> Labels: hotdeploy
> Fix For: 3.0-beta-2
>
>
> First need to set the server in development mode:
> 1 modify the config.xml:
> <module name="org.apache.geronimo.configs/tomcat7-deployer/3.0-beta-2-SNAPSHOT/car">
> <gbean name="TomcatWebBuilder">
> <attribute name="jspServlet" 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-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>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>
> </servlet>
> </web-app:web-app>
> </attribute>
> </gbean>
> </module>
> ...
> <module name="org.apache.geronimo.configs/jasper-deployer/3.0-beta-2-SNAPSHOT/car">
> <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>
> </module>
> 2 set GERONIMO_OPTS
> set GERONIMO_OPTS=-Dorg.apache.geronimo.webapplication.stage=DEVELOPMENT
> Steps:
> 1. Install wep and OSGi tool in a clean eclipse
> 2. Install wasce
> 3. Import the attached sample eba into eclipse
> 4. Modify server configuration to enable hot swap, then run the sample on the defined server
> 5. Open a browser to visit the jsp url
> 6. Update a jsp file and save it
> 7. Check if the jsp is updated by reloading the jsp url
> Symptom: you will see the jsp is not updated.
--
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