Thanks Deepal that worked. I can see the wsdl. However, when i access the endpoint directly, by dropping the ?wsdl I get Requested Object Not Found.

I can still hit the endpoint from any web service client, its just that from within the console, i cannot hit it directly.

This is no big deal, but just wanted to know if anyone else had come across this?

Deepal Jayasinghe wrote:
can you pls have a look at the link

http://www.wso2.net/faqs/axis2/java/q11

Cleve OpenSource wrote:

I've read all i can about WSDL generation from Axis 2, this is what I
have:

1) document style web service
2) xml beans data binding and a custom message handler
3) placed my wsdl in the aar's META-INF directory

However, i cannot get the WSDL sent back to me when i issue:
http://<service>:<port>/<contextpath>/services/booking?wsdl

the structure of my aar is this:

booking.aar
--META-INF
----services.xml
----booking.wsdl
....

and the services.xml contains the following:

<service name="booking" scope="application">
   <messageReceivers>
     <messageReceiver mep="http://www.w3.org/2004/08/wsdl/in-out";
class="cces.xjmi.ws.booking.v10.XjmiBookingWebServiceMessageReceiverInOut"/>

   </messageReceivers>
   <parameter name="ServiceClass"
locked="false">cces.xjmi.service.XjmiBookingWebServiceSkeleton</parameter>

   <operation name="addBooking"
mep="http://www.w3.org/2004/08/wsdl/in-out"/>
   <operation name="modifyBooking"
mep="http://www.w3.org/2004/08/wsdl/in-out"/>
   <operation name="cancelBooking"
mep="http://www.w3.org/2004/08/wsdl/in-out"/>
   <operation name="ping" mep="http://www.w3.org/2004/08/wsdl/in-out"/>
</service>


The web service works fine but cannot any see why i'm still get the
dreaded error message.  It's just plain weird...

<error>
<description>Unable to generate WSDL for this service</description>
   <reason>
Either user has not dropped the wsdl into META-INF or operations use
message receivers other than RPC.
</reason>
</error>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to