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 jboss.ws:di=cm.ear/cm.ejb3,port=SchedulerWSBeanPort,service=SchedulerWSBeanService http://myhost:8080/cm/SchedulerWSBean?wsdl
Anyone else? I am the only one who cannot get a WSDL to display on jboss 4.0.4GA patch1 (ejb3)?
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.
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.
I got the same problem as you.. would you be able to share you solution if you find it.
thanks a lot...
I have not gotten a solution to it yet. I tried upgrading to the latest WS release to no avail. Please let me know if you find a solution.
Anyone else? Is there something I am missing?
I am just wondering if it's necessary to add the web service session bean to ejb-jar.xml
here is what I saw in http://docs.jboss.org/jbossas/jboss4guide/r2/html/ch12.html
<?xml version="1.0" encoding="UTF-8"?> <ejb-jar xmlns="http://java.sun.com/xml/ns/j2ee" version="2.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd"> <display-name>chapter 12 EJB JAR</display-name> <enterprise-beans> <session> <ejb-name>HelloBean</ejb-name> <service-endpoint>org.jboss.chap12.hello.Hello</service-endpoint> <ejb-class>org.jboss.chap12.hello.HelloBean</ejb-class> <session-type>Stateless</session-type> <transaction-type>Container</transaction-type> </session> </enterprise-beans> <assembly-descriptor> <method-permission> <unchecked/> <method> <ejb-name>HelloBean</ejb-name> <method-name>*</method-name> </method> </method-permission> <container-transaction> <method> <ejb-name>HelloBean</ejb-name> <method-name>*</method-name> </method> <trans-attribute>Required</trans-attribute> </container-transaction> </assembly-descriptor> </ejb-jar>
also it seems a webservice.xml is needed..
do you have all these in place?
Thanks for the reply.
If that is the case, it is a bit disppointing since with EJB 3 you no longer need descriptor files. So does this mean that JSR 181 is not completely annotation driven?
you are right though, just found the descriptor is not for ejb3, there is no annotation in the session bean for the example...
my problem is
javax.xml.rpc.ServiceException: Error processing WSDL document: java.io.FileNotFoundException: http://localhost:8080/regserver/CalculatorBean?WSDL
after deploy, the IDE automatically generated a wsdl file and saved in
I think it's necessary to place the file somewhere so that the client can access it via http://localhost:8080/regserver/CalculatorBean?WSDL(in my case)..need to find out how...
Would you look at my post (the 6th one) and answer my quetions? I think I can help you.
Are you packaging your application inside an EAR? Do you have a WAR inside your EAR?
I have EJB3 + WebServices working like a charm.
Thank you for trying me again. I did not see your question.
Yes, I do have a WAR packaged in my ejb file. Is that the issue? The web services is supposed to outside of the WAR that is included which is only there for a JNLP based application.
Thank again! If I can get this working, it will be quite a relief.