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

[Aaron Pestel (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12449359#action_12449359 ] 

Aaron Pestel commented on JBIDE-3607:
-------------------------------------

Probably, I hadn't even thought of that.  I was suggesting it because I thought it was more consistent with the way Dynamic Web Projects work.  I thought if I:  1.) had a JSP that referenced a Java class, 2.) modify the Java class, 3.) republish, 4.) see the change that I made in my Java class that the JSP was using.  I just tried that to make sure that was the behaviour the Dynamic Web Project had, and I was wrong.  The Dynamic Web Project behaves the same as the ESB project.  In a Dynamic Web Project, I don't actually see changes to the Java classes on the server when I republish the project - unless I modify the web.xml.

So, I would recommend closing this Jira with no changes as ESB project behaviour is consistent with Dynamic Web Project behaviour (and probably all Java Eclipse projects' behaviour likely because of the reason you gave - it's been too long since I made my living as a developer  :-) ).   

> 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