[
https://issues.jboss.org/browse/AS7-659?page=com.atlassian.jira.plugin.sy...
]
Fred Bricon commented on AS7-659:
---------------------------------
Just got hit by the same issue while testing changes on JSPs. As I can understand you
don't want to enable dev mode by default, how about triggering that dev mode by an
environment variable on startup? We could then adjust the default environment settings
directly in JBoss Tools' runtime launch configuration.
WDYT?
Enable JSP dev mode by default in standalone configuration
----------------------------------------------------------
Key: AS7-659
URL:
https://issues.jboss.org/browse/AS7-659
Project: Application Server 7
Issue Type: Enhancement
Components: Web
Affects Versions: 7.0.0.Beta3
Reporter: jaikiran pai
Assignee: jaikiran pai
Currently any changes to a .jsp file (in an exploded deployment) are *not* picked up
dynamically and instead requires a application redeployment. This can be enabled currently
by adding the jsp dev mode configuration to standalone.xml as follows:
{code:xml}
<subsystem xmlns="urn:jboss:domain:web:1.0">
<configuration>
<jsp-configuration development="true" />
</configuration>
<connector name="http" protocol="HTTP/1.1"
socket-binding="http" scheme="http"/>
<virtual-server name="localhost">
<alias name="example.com"/>
</virtual-server>
</subsystem>
{code}
It would be very useful if the server, by default, enabled this configuration and picked
up the changes to jsps dynamically (like it used to do in previous AS version).
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira