I guess that you are packaging a ".war" inside your EAR. Right?
If it is so, try changing the war's context root to anything but "cm". I.E.,
"cmweb".
Repackage your EAR.
Redeploy your EAR and you should be able to access the WebService.
Let me know if it works.
View the original post :
http:
Anybody else?
The EJB Web Service appears to be deployed correctly and shows up in the
http://:8080/jbossws page. The WSDL listed in the console however still does
not work (404).
Anything else I need to do? I am using JBoss 4.0.4 GA Patch 1.
View the original post :
http://www.jboss.com/ind
Anyone else? I am the only one who cannot get a WSDL to display on jboss
4.0.4GA patch1 (ejb3)?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3953289#3953289
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3953289
Using
Thank you. That returned the WSDL to the endpoint. However, when I followed
the link to the WSDL, I get a 404 error. Is there a problem with the endpoint?
I did not see any errors in the log?
Thank in advance.
Registered Service Endpoints
| ServiceEndpointID ServiceEndpointAddress
|
Try http://localhost:8080/jbossws in any web browser.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3953162#3953162
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3953162
Using Tomcat but need to do more? Need to suppor