you should set auto-deploy-exploded not to 'true' as this will enable the scanner to watch each file and deploy the application on any change.
set false and use the mwebapp.ear.dodeploy file to deploy and redeploy if necessary.
I set the auto-exploded to 'false', changed 1 jsp file in exploded war folder and force deployed using myapp.ear.dodeploy. Still the same issue. It brings down the entire webapp and redeploys entire webapp with new jsp change. I need ways so that the entire webapp does not re-deploy but just this 1 jsp change gets 'HOT'(not Auto) deployed. Thanks
7.1.1 has known issue with jsp configuration not being aplied at all.
this has been fixed few days after 7.1.1 was released, try using any version after that. i would recomend 7.2.0 / eap 6.1 alpha
Hi Tomaz, Thanks for response.
I tried both 6.1.0.Alpha and 6.1.0.Final.
Here is the configuration for my web subsystem.
<subsystem xmlns="urn:jboss:domain:web:1.1" default-virtual-server="default-host" native="true">
<connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http"/>
<connector name="ajp" protocol="AJP/1.3" scheme="http" socket-binding="ajp"/>
<virtual-server name="default-host" enable-welcome-root="true">
Here is the deployed app folder structure under deployments folder
myapp.ear <--this is a folder
mywebapp.war <--this is a folder
If auto deploy exploded setting is false, jboss does nothing when i edit a jsp in deployments folder so i am still seeing old page.
If auto deploy exploded setting is true, JBoss does a full redeploy of webapp, which i don't want. Problem with the full redeploy is that it brings down the webapp and the entire http session so i have to log back in again to test my change. This is not ideal in development time.
Pls let me know if something does not look right. Thanks.
From what I see in my EAP 6 installation, the version of the web subsystem is (at least) 1.4. Make sure you have that right.
I have exactly the same problem.
Is there anyone that can help ?
Best Regards and Thanks