Hi Thomas, Thanks for answering. I need to be able to deploy web services to both connectors, not just the new one, so I think the link you referred (which, by the way, i already knew) is not applicable.
I thought that there could be more than meets the eye in your answer, so I reverted the new service creation and moved the new connector definiton into the jboss.web service definition, along with the other connectors 8080, and 8443 already there. Then I hard coded in one of the web service's wsdl a url to the alternative (8081) connector url. I ignored the test deployment directory and deployed this web service in the all/deploy directory, but as expected that hard coding only reflects upon the deployed wsdl. During this deployment i still get the message that the web service is being deployed in the connector associated with the definitons in the ws4ee jboss-service.xml (8080). Note that I set the to "false". So, unless I'm missing something obvious, this is not a viable solution to my problem. How can I attach ws deployments to differents connectors ? With servlets, the new tomcat service definition solved it, but how can I trigger wsdeployer when i deploy services in the directory attached to the other service/connectors ? As explained in my original question, that is simply not working. Hey! I'm even open to manualy deploy the ws artifacts. Is this viable ? Any other thoughts ? anyone ? Please do not assume I'm not trying to solve this concurrently. this is no a question of dumping my work on another persons' shoulders. My need for help is still quite real. Thank you very much. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3950402#3950402 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3950402 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
