JBoss 7.1.1 Final JSP Thermal Deployment Solution in debug environment--Go

The company's website system used in the middle is jboss7.1.1 Final, because some data and service testing environment does not have, it is unavoidable to debug some JSP pages in the test environment, found the JBoss application downloaded from the JBoss community has a problem, the new JSP page will be deployed in real-time, The modified JSP page will not be deployed properly.
The latest find out the following solutions:
Found <subsystem xmlns= "urn:jboss:domain:web:1.0" in the Jboss7\standalone\configuration\standalone.xml file Default-virtual-server= "Default-host" > do the following configuration

XML code

1. <Subsystemxmlns="Urn:jboss:domain:web:1.0"Default-virtual-server="Default-host"><Configuration><Jsp-configurationDevelopment="True"/></Configuration><ConnectorName="http"Protocol="http/1.1"socket-binding="http"Scheme="http"/><Virtual-serverName="Default-host"enable-welcome-root= "true" >                  <alias  name= "localhost" />                   <alias name= "example.com" />              </virtual-server>          </subsystem>    

To open development mode. But after adding the code, the discovery does not work. There were numerous postings to the JBoss community and found Tomaz Cerar as described below:
In 7.1.1 we had included much reworked web subsystem but Unfortunaly I missed a bit that coused all JSP configuration to Be ignored.
That bug was a fixed soon after 7.1.1 were released and is now part of 7.1.2 and 7.2.x Development Branch.
Plain connection https://community.jboss.org/message/723813 This is a bug in this version, which is said to be repaired later. But for the intermediate upgrade risk is very large, many businesses are based on the old version of the development, in order to be safe, I would like to be sure that some people do not have to upgrade the problem has been resolved.
Lights Dim, found the answer:
1. Sure to add
<configuration>
<jsp-configuration development= "true"/>
</configuration>
In Standalone.xml under <subsystem xmlns= "urn:jboss:domain:web:1.1" default-virtual-server= "Default-host" native= "False" >

2. Go to Jboss-as-7.1.1.final/modules/org/jboss/as/web/main
Place the Jboss-as-web-7.1.1.final-recompile.jar in there. Can download from http://www.datafilehost.com/download-2cb9ff04.html

3. Open Module.xml (Jboss-as-7.1.1.final/modules/org/jboss/as/web/main) and add the following line
<!--resource-root path= "Jboss-as-web-7.1.1.final.jar"/-->
<resource-root path= "Jboss-as-web-7.1.1.final-recompile.jar"/>
The narrative is very simple, I will not translate
See the original: https://community.jboss.org/message/723945#723945#723945
According to the author's method of operation, the problem miraculously solved, at that time because the JBoss core package has been recompiled, whether there is any hidden danger still needs to be thoroughly tested.
The package that the solution provider recompiled was also provided in the attachment, and I tested it for no problem.
Now share with you.

Original: http://andy-li-chn.iteye.com/blog/1966986