[ https://jira.jboss.org/jira/browse/JBESB-2870?page=com.atlassian.jira.plu... ] Kevin Conner commented on JBESB-2870: ------------------------------------- The esb deployment should only error if you embed a war which included a WS. This is/was a bug in the JBossWS deployer on AS 4.x. -- 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/JBESB-2870?page=com.atlassian.jira.plu... ] David Ward reassigned JBESB-2870: --------------------------------- Assignee: David Ward -- 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/JBESB-2870?page=com.atlassian.jira.plu... ] Tom Fennelly commented on JBESB-2870: ------------------------------------- What's the status of 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

[ https://jira.jboss.org/jira/browse/JBESB-2870?page=com.atlassian.jira.plu... ] Kevin Conner commented on JBESB-2870: ------------------------------------- The following requirements are from David "The affected quickstarts are webservice_proxy_basic webservice_proxy_routed webservice_proxy_security webservice_proxy_versioning In each of these quickstarts, a .war archive is first "pre"-deployed to JBossESB, then after a short sleep, a .esb archive is deployed. The reason is that in each .esb, the jboss-esb.xml uses a SOAPProxy action to point to a wsdl URL exposed (via JBossWS) by the .war archive. The crux is that the .war archive *has* to be deployed first so that the SOAPProxy can call upon it to get the WSDL. I would like it to be so that in deployment.xml one can specify somehow that if the .ear gets deployed first, and there is a dependency on the .war, that the .war's deployment will get triggered first. This could happen if both the .war and .ear exist in JBoss' deploy directory during a re-start. Please note that this is *not* to say that the .war's web service has to be available publicly via Tomcat's http Connector. If the wsdl property of SOAPProxy is configured with an "internal://" URL (instead of "http(s)://"), then JBossWS' internal API is used to get the wsdl." This mechanism is not intended to be a supported mechanism, just one that we can use to guarantee external wars can exist as a dependency within these quickstart esbs. Some type of barrier mechanism is probably the best bet, with the esb depending on the barrier and the war signalling it when started. -- 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/JBESB-2870?page=com.atlassian.jira.plu... ] Work on JBESB-2870 started by Tom Fennelly. -- 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/JBESB-2870?page=com.atlassian.jira.plu... ] Kevin Conner commented on JBESB-2870: ------------------------------------- Could your barrier not query the currently deployed objects on startup? It could then determine whether it has already been deployed and trigger the barrier, allowing the esb to only depend on the barrier and the war to deploy normally. -- 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/JBESB-2870?page=com.atlassian.jira.plu... ] Tom Fennelly commented on JBESB-2870: ------------------------------------- I fixed this using a JMX Barrier based on the JMX notifications for the webservices in question. (Checked in). This requires a -services.xml file to be added for each quickstart, defining a barrier controller for each webservice in question. I also created a JMX Barrier version based on notifications for war deployments, which can be configured centrally in the jbossesb.esb. (Not checked in) With this version, you don't require the -services.xml files in the quickstarts. In case we ever needed anything like it again, I added the code in an SVN workspace: https://svn.jboss.org/repos/labs/labs/jbossesb/workspace/tfennelly/war-de... -- 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