Yes the answer is fairly simple. In the axis2.xml it defines "default" message receivers. You only overrode the MR for one operation. Now admittedly you only had the one operation, but Axis2 didn't realise. So it looked at the service, saw there is no MR defined for the service, looked at the default. The default is RawXML, which it cannot create WSDL for, so it decided that it couldn't generate WSDL.
Does that make sense? Paul On Feb 12, 2008 2:29 PM, Paulo Carvalho <[EMAIL PROTECTED]> wrote: > Hello > > Thanks for your quick answer. Your solution have resolved my problem. > But I would like to know why. Do you know? > > thanks again > > regards > > > > On 2/12/08, Paul Fremantle <[EMAIL PROTECTED]> wrote: > > > > > > > > Rather than specifying a per-operation message receiver, try using the > > standard message receiver config from the sample pojo service: > > <messageReceivers> > > <messageReceiver mep="http://www.w3.org/2004/08/wsdl/in-only"; > > > > class="org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver"/> > > <messageReceiver mep="http://www.w3.org/2004/08/wsdl/in-out"; > > > > class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/> > > </messageReceivers> > > > > Paul > > > > On Feb 12, 2008 9:24 AM, Paulo Carvalho <[EMAIL PROTECTED]> wrote: > > > > > > Hello > > > > > > I am new using Axis2 and I am having a problem. I already search over > the > > > net to find the solution for my problem, but everything looks fine for > me. > > > > > > 1 - I am using the last version of Axis2. > > > > > > 2 - I have a class called MyApp (in the app package) with the method > Send > > > > > > 3 - My services.xml file is the following one: > > > > > > <serviceGroup> > > > <service name="MyService"> > > > <description>My service</description> > > > <parameter name="useOriginalWSDL">false</parameter> > > > <parameter name="ServiceClass" > > > locked="false">app.MyApp</parameter> > > > <operation name="Send"> > > > <messageReceiver > > > class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/> > > > </operation> > > > </service> > > > </serviceGroup> > > > > > > 4 - The webservice is deployed with success > > > > > > 5 - When I try to access to this WSDL > > > (http://localhost:8084/MyWS/services/MyService?wsdl) I have the > following > > > message/reason appearing on my browser instead of the WSDL: > > > > > > > > > <error> > > > <description>Unable to generate WSDL for this service</description> > > > <reason> > > > If you wish Axis2 to automatically generate the WSDL, then please use > one > > > of the RPC message receivers for the service(s)/operation(s) in > > > services.xml. If you have added a custom WSDL in the META-INF directory, > > > then please make sure that the name of the service in services.xml > > > (/serviceGroup/service/@name) is the same as in the custom wsdl's > service > > > name (/wsdl:definitions/wsdl:service/@name). > > > </reason> > > > </error> > > > > > > > > > Can anyone help me with that? > > > > > > > > > Thanks > > > > > > Best regards > > > > > > Paulo > > > > > > > > -- > > Paul Fremantle > > Co-Founder and VP of Technical Sales, WSO2 > > OASIS WS-RX TC Co-chair > > > > blog: http://pzf.fremantle.org > > [EMAIL PROTECTED] > > > > "Oxygenating the Web Service Platform", www.wso2.com > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > -- > Paulo Carvalho > 1 rue du Chateau > 57710 Aumetz > France > www.antikuado.com > www.sunofportugal.com -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
