[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-3607) ESB Project Republish Not Republishing

Max Rydahl Andersen (JIRA) jira-events at lists.jboss.org
Thu Jan 22 16:46:44 EST 2009


     [ https://jira.jboss.org/jira/browse/JBIDE-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Max Rydahl Andersen updated JBIDE-3607:
---------------------------------------

    Fix Version/s: 3.0.0.GA
                   3.1.0


the problem with this is that it will trigger restarts even when you don't.

Example:

1) Deploy your project
2) Put a breakpoint in a java class
3) trigger whatever is needed to hit breakpoint in #2
4) the breakpoint hits and you alter the .java file
5) Press Save.

What do you expect the next step is ?

*I* would like java's hot replace of java classes to just work and not see any restart of the application since that will possible trigger concurrent triggers or similar behavior you don't want in a debug situation.

If we do what you suggest debugging becomes hard, don't you agree ?

> 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
>             Fix For: 3.0.0.GA, 3.1.0
>
>
> 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

        



More information about the jbosstools-issues mailing list