[
https://jira.jboss.org/browse/JBDS-1309?page=com.atlassian.jira.plugin.sy...
]
Rob Stryker commented on JBDS-1309:
-----------------------------------
This is 100% the design of the server. This is not a bug. This works as designed.
The server simply does not scan for java changes in most deployments for hot-code
replacement. It only knows to redeploy the app if the descriptor file is touched, or
possibly the containing folder. Non-java changes (in web projects at least) can be
instantly realized (html, etc) but this varies per deployment type, and class files are
almost never instantly reloaded except in Seam projects, which have a hot-deploy folder
and their deployer on the server knows what to look for.
ESB project not being redeployed
--------------------------------
Key: JBDS-1309
URL:
https://jira.jboss.org/browse/JBDS-1309
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: SOA Platform
Affects Versions: 3.0.0.GA
Reporter: Jehudi Castro
Assignee: Rob Stryker
Fix For: 3.0.2.GA, 4.0.0.Beta2
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
I have a server configured in the IDE and an ESB project configured to run in the server,
when I only change a java file (a custom action) in the project, it does not reflect the
changes in the ruining server (although I see the message "Publishing to
server..." in the Progress view for some seconds), however if I touch the
jboss-esb.xml the project is redeployed correctly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira