[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-5870) Cannot create JbossWS service with client enabled

[ https://jira.jboss.org/jira/browse/JBIDE-5870?page=com.atlassian.jira.plu... ] Brian Fitzpatrick commented on JBIDE-5870: ------------------------------------------ I take that back... It does work, but it still gives me the Selection Must Be WSDL message for some reason. If I remove the project from the server and put it back on the server, it deploys fine and the JbossWS console can see it. But the wizard is deploying it to: 08:07:04,457 INFO [TomcatDeployment] deploy, ctxPath=/webJBIDE5870d 08:07:04,585 INFO [WSDLFilePublisher] WSDL published to: file:/NotBackedUp/bfitzpat/runtimes/jboss-soa-p.5.0.0/jboss-as/server/default/data/wsdl/webJBIDE5870dEAR.ear/webJBIDE5870d.war/Hello4060797287880385934.wsdl And it's resolving to an endpoint of: Endpoint Name jboss.ws:context=webJBIDE5870dEAR-webJBIDE5870d,endpoint=JbossWS Endpoint Address http://localhost:8080/webJBIDE5870dEAR-webJBIDE5870d/JbossWS?wsdl This doesn't work for the JBossWS console. It can't find it. But if you cancel the wizard after it fails and undeploy the EAR from the server, then redeploy it, it works. There is an application.xml in the EAR in both cases, but for some reason it's not deploying correctly from the wizard. -- 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