[
https://jira.jboss.org/jira/browse/JBIDE-3607?page=com.atlassian.jira.plu...
]
Aaron Pestel commented on JBIDE-3607:
-------------------------------------
Correct. I would probably say it's not automatically redeploying, rather than not
restarting, but I'm guessing that is what you meant. It probably would work to
"touch" the jboss-esb.xml file after changing any other files in the ESB
project.
ESB Project Republish Not Republishing
--------------------------------------
Key: JBIDE-3607
URL:
https://jira.jboss.org/jira/browse/JBIDE-3607
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Environment: JBDS
Version: 2.0.0.CR1
Build id: R200812221144
Build date: 12/22/2008 11:54
Reporter: Aaron Pestel
Create a new ESB project and add it to a SOA-P server. If I modify the jboss-esb.xml
file and save the project, the project shows that it needs to republished, and after
republishing, changes are reflected on the server. Watching the server log, you can see
the ESB archive get undeployed and then deployed as one would expect as part of
republishing.
Now, instead of changing jboss-esb.xml, change a Java custom action also in the ESB
project and save it. The project will correctly show that it needs to be republished, but
if you republish it, the changes do not actually make it to the server (I don't see
the server log show undeploying and redeploying the ESB archive and the changes made to
the Java file do not take effect on the server).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira