[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-5597) Full Publish of ESB projects does not redeploy and also can't deploy at all from eclipse workspace directory (deploy option)

[Aaron Pestel (JIRA)]

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

Aaron Pestel commented on JBIDE-5597:
-------------------------------------

Did some more digging and created a test case.  I'm not sure if this is actually a JBDS problem or a SOA-P problem - or I suppose it could be user error as well.  :-)

I've attached a simple JBDS 3.0 ESB project that uses the new HTTP gateway.  To reproduce:

1.)  Import the project into JBDS 3.0 M4
2.)  Start SOA-P 5 Beta
3.)  Add the TestDeploy projet to the SOA-P 5 Beta server
4.)  Should see these lines printed to the console

09:36:31,856 INFO  [EsbDeployment] Starting ESB Deployment 'TestDeploy.esb'
09:36:31,912 INFO  [TomcatDeployment] deploy, ctxPath=/TestDeploy
09:36:31,977 WARNING [config] Unable to process deployment descriptor for context '/TestDeploy'
09:36:31,978 INFO  [config] Initializing Mojarra (1.2_13-b01-FCS) for context '/TestDeploy'

5.)  Open a browser window and hit this URL "http://localhost:8080/TestDeploy/http/testDeploy"
6.)  Should get an empty screen in the browser
7.)  Should see this in the server console

09:37:11,643 INFO  [STDOUT] Message #1: 
09:37:11,643 INFO  [STDOUT] [].

8.)  In JBDS edit jboss-esb.xml and change "Message #1" to "Message #2"
9.)  Save jboss-esb.xml
10.)  Note that the JBoss Server View shows it needs republished

TestDeploy[Republish]

11.)  Right-click on "TestDeploy[Republish]" and choose "Full Publish"
12.)  Note it shows as synchronized
13.)  Note that the jboss-esb.xml file in the server deploy directory was actually updated (makes me think it's maybe an ESB issue)
14.)  Open a browser window and hit this URL "http://localhost:8080/TestDeploy/http/testDeploy"
15.)  Note that the server console still shows Message #1 instead of Message #2

09:48:51,343 INFO  [STDOUT] Message #1: 
09:48:51,343 INFO  [STDOUT] [].

16.)  Also note that it doesn't show the ESB service being undeployed and redeployed as JBDS 2.1 used to.

17.)  Now, right-click on the server and remove the project from the server.
18.)  Note in the server console that it has been removed

09:50:16,501 INFO  [TomcatDeployment] undeploy, ctxPath=/TestDeploy
09:50:16,519 INFO  [EsbDeployment] Stopping 'TestDeploy.esb'
09:50:16,558 INFO  [EsbDeployment] Destroying 'TestDeploy.esb'
09:50:16,559 WARN  [ServiceMessageCounterLifecycleResource] Calling cleanup on existing service message counters for identity ID-7

19.)  Double click on the server in JBoss Server View to edit server properties
20.)  Click the "Deployment" tab in the editor window that opens
21.)  Select "Use Workspace Metadata" radio button
22.)  Click "File | Save"
23.)  Right-click on the server and add the TestDeploy project to it again
24.)  Note that it shows it there in the JBoss Server View as synchronized, but no log messages were printed to the console showing it deployed like there were in step #4
25.)  Hit "http://localhost:8080/TestDeploy/http/testDeploy" in a browser and note the 404 error because the service is not deployed

26.)  Undeploy the project from the server, restart the server, add the project back to the server
27.)  Now, it shows getting deployed

09:56:28,557 INFO  [EsbDeployment] Starting ESB Deployment 'TestDeploy.esb'
09:56:28,621 INFO  [TomcatDeployment] deploy, ctxPath=/TestDeploy
09:56:28,675 WARNING [config] Unable to process deployment descriptor for context '/TestDeploy'
09:56:28,675 INFO  [config] Initializing Mojarra (1.2_13-b01-FCS) for context '/TestDeploy'

28.)  Now it seems to work deploying from the workspace folder, however if you change the jboss-esb.xml file again and republish, the changes are still not picked up and hitting the service via the browser still shows the old "Message #..." that was configured in the initial publish.

So, two issues:

A.)  Can't see to get changes to jboss-esb.xml to actually get replublished without remove/add to server each time.
B.)  Can't change to deploy from workspace folder (even though JBDS makes it look like it worked) without restarting server


> Full Publish of ESB projects does not redeploy and also can't deploy at all from eclipse workspace directory (deploy option)
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-5597
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-5597
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>    Affects Versions: 3.1.0.M4
>         Environment: Fedora 9, SOA-P 5.0 Beta1, JBDS 3 M4
>            Reporter: Aaron Pestel
>            Assignee: Rob Stryker
>             Fix For: 3.1.0.CR2
>
>         Attachments: TestDeploy.zip
>
>
> Create a new ESB project, add it to a SOA-P server, in the JBossAS view, right-click on the project and choose "Full Publish" - it doesn't republish the project like it used to.  Can also modify the project (jboss-esb.xml) and select full publish and it still won't republish, have to remove project from server and re-add project to server.
> JBDS project now seems to be setup by default to deploy to JBoss deploy directory as opposed to the Ecplise workspace.  I changed it to deploy to the workspace (like I think previoius versions defaulted to), and couldn't even get the project to deploy that way.
> If this isn't reproducible enough, please let me know and I'll attach a project with more clear steps.
> Thanks!

-- 
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