aspose file tools*
The moose likes Web Services and the fly likes jaxws no corresponding wsdl operation error Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Web Services
Bookmark "jaxws no corresponding wsdl operation error" Watch "jaxws no corresponding wsdl operation error" New topic
Author

jaxws no corresponding wsdl operation error

Dan Badham
Greenhorn

Joined: Feb 19, 2011
Posts: 3
Hi there,

I have been developing a jaxws webservice using netbeans6.9.1 and glassfishv3. The webservice has been working fine until recently when I have added some new operations.

Once such new operation is as follows:


When I try to use the Web Service tester I get the following error:

Exceptions details : javax.xml.ws.WebServiceException: Method getAllQuestions is exposed as WebMethod, but there is no corresponding wsdl operation with name getAllQuestions in the wsdl:portType{http://webservice.ejb.proposal.stfc.uk/}ProposalAPI

However in the wsdl that is deployed on the server I have the operation:



So I do not understand this error as the operation does exist, I have done countless rebuilds and redeploys etc but the problem still persists, I have tried deploying from netbeans and manually to glassfish directly.

So if anyone has experienced this issue before or has some debugging sugguestions then that would be very much appreciated.
Ivan Krizsan
Ranch Hand

Joined: Oct 04, 2006
Posts: 2198
    
    1
Hi!
Others have encountered the same problem: http://metro.1045641.n5.nabble.com/Webservice-Client-Error-XXXX-is-exposed-as-WebMethod-but-there-is-no-corresponding-wsdl-operation-td1067308.html
It would be interesting to see your complete WSDL.
Best wishes!


My free books and tutorials: http://www.slideshare.net/krizsan
Dan Badham
Greenhorn

Joined: Feb 19, 2011
Posts: 3
Thank you for your reply.

It is interesting that someone else has a similar sort of issue but is running tomcat, I had assumed it may have been a glassfish issue as I have had trouble with glassfish and webservices in the past.

However I have managed to get my webservice running again with the new operations by deploying it to a fresh installation of glassfish, hopefully I won't need to do this everytime I add a new operation!

When I get some free time I will investigate the original problem some more, as it is likely to happen again.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: jaxws no corresponding wsdl operation error