DescriptionJose Roman Martin Gil
2015-05-19 18:37:41 UTC
Description of problem:
JBoss EAP in Standalone Mode reload JSP when you redeploy a new version of a application, however JBoss EAP in Domain Mode do that only when you restart the server group where the application is assigned.
In both cases the development attribute in web subsystem is defined as false.
<subsystem xmlns="urn:jboss:domain:web:2.2" default-virtual-server="default-host" native="false">
<connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http"/>
<virtual-server name="default-host" enable-welcome-root="true">
<alias name="localhost"/>
<alias name="example.com"/>
</virtual-server>
</subsystem>
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Starts JBoss EAP in Domain Mode
2. Starts a Server Group
3. Deploy a new Web Application with a index.jsp file with title "version 1.0"
4. Test the application v.1.0
5. Change title "version 2.0" in index.jsp file
6. Redeploy the application
7. Test the application v.2.0
Actual results:
The title showed is "version 1.0"
Expected results:
The title must be "version 2.0"
Additional info:
Only when the server group is restarted then "version 2.0" is showed.
There is a KCS (https://access.redhat.com/solutions/334963) with a solution about that: activate development attribute. However it is not recommended for a production environment.
It is not a solution activate it because it is needed to be applied in a production environment.
The right behaviour is do the same as in Standalone Mode (with out restart servers).
Description of problem: JBoss EAP in Standalone Mode reload JSP when you redeploy a new version of a application, however JBoss EAP in Domain Mode do that only when you restart the server group where the application is assigned. In both cases the development attribute in web subsystem is defined as false. <subsystem xmlns="urn:jboss:domain:web:2.2" default-virtual-server="default-host" native="false"> <connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http"/> <virtual-server name="default-host" enable-welcome-root="true"> <alias name="localhost"/> <alias name="example.com"/> </virtual-server> </subsystem> Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Starts JBoss EAP in Domain Mode 2. Starts a Server Group 3. Deploy a new Web Application with a index.jsp file with title "version 1.0" 4. Test the application v.1.0 5. Change title "version 2.0" in index.jsp file 6. Redeploy the application 7. Test the application v.2.0 Actual results: The title showed is "version 1.0" Expected results: The title must be "version 2.0" Additional info: Only when the server group is restarted then "version 2.0" is showed. There is a KCS (https://access.redhat.com/solutions/334963) with a solution about that: activate development attribute. However it is not recommended for a production environment. It is not a solution activate it because it is needed to be applied in a production environment. The right behaviour is do the same as in Standalone Mode (with out restart servers).