Hi,
MTOM sample is designer to work in the OM level.. It takes OMElement as input and returns OMElement... That's why it uses the RawXmlMessageReciever.. This will not generate a usable WSDL , but you should be able to code generate for the given WSDL.. Notice the following..
<xs:element type="xs:anyType" name="return"/>

We have to custom write a WSDL and need to put it in to the .aar so that it'll display when user asks......

~Thilina

On 6/12/06, Hoda Nadeem <[EMAIL PROTECTED]> wrote:
 
Thanks Jeff. That worked perfectly.
 
Nadeem


From: Scudder, Jeffrey W [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 08, 2006 5:27 PM
Subject: RE: [Axis2] MTOM example wsdl generation fails

Hi Nadeem,
 
I was told to change RawXMLINOutMessageReceiver to RPCMessageReceiver in the services.xml file of the service. The RawXMLINOutMessageReceiver is designed to not produce a WSDL.
 

<messageReceiver class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/>

<messageReceiver class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/>

Hope this helps

-Jeff



From: Hoda Nadeem [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 08, 2006 2:17 PM
To: [email protected]
Subject: [Axis2] MTOM example wsdl generation fails

 
I'm running the MTOM sample in the Axis2 1.0 release, and I am able to deploy the service, and talk to the server using the sample GUI web client successfully.
 
But... when I try to go to the wsdl through the admin interface, I get the following error:
 
 
<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>
 
Is there a reason why Axis2 is not able to auto-generate the WSDL for the MTOM sample out-of-the-box?
 
I am using Weblogic 9.1 for Axis2 deployment.
 
Thanks.
 
Nadeem



--
"May the SourcE be with u"            
http://webservices.apache.org/~thilina/
http://thilinag.blogspot.com/                 http://www.bloglines.com/blog/Thilina              

Reply via email to