[ https://jira.jboss.org/jira/browse/JBDS-1026?page=com.atlassian.jira.plug... ] Aaron Pestel updated JBDS-1026: ------------------------------- Component/s: SOA Platform -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5597?page=com.atlassian.jira.plu... ] Max Rydahl Andersen updated JBIDE-5597: --------------------------------------- Fix Version/s: 3.1.0.CR2 Assignee: Rob Stryker The deploy destination depends on how the server were installed into JBDS. How are you deciding whether something is published or not ? Looking at the actual files ? Where did you look ? Anything in the error log ? anything in the server log ? -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5597?page=com.atlassian.jira.plu... ] 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 -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5597?page=com.atlassian.jira.plu... ] Rob Stryker resolved JBIDE-5597. -------------------------------- Resolution: Partially Completed To be clear, when the server is started up is when it adds all the possible locations for the deployment scanner to scan. So modifying the deployment page or enabling custom folders for each module will *not* be recognized without a server restart. However I have now fixed it so that it should recognize a switch to any folder already mentioned in the editor before startup. To be clear, the suggested policy of changing a project's deploy location is: 1) UNDEPLOY the module so it is removed from the old legacy location 2) change the module's deploy location in the editor 2a) If the server is started and the new deploy location is one that likely was unknown by the tooling during the initial startup, restart the server 3) redeploy the module -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5597?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on JBIDE-5597: -------------------------------------------- btw. beyond that the underlying issue for the redeploy is the runtime since JBDS actually *does* deploy the files - there is another issue for that somewhere. -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-5597?page=com.atlassian.jira.plu... ] Rob Stryker resolved JBIDE-5597. -------------------------------- Resolution: Done "Shouldn't the server editor for deployment location state this important and crucial piece of information ? i.e. "Changes in this view does not take affect before server have been restarted" or something ?" Yes, and the server editor's deployment page now says something like this. -- 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