Yes Guillaume. The wsdl uses doc/lit binding. I agree that the wsdl creation has a problem. But I think XFire is using the generated wsdl for processing the request rather than using the wsdl we provide as a property. That's why I am getting a SOAPFault saying : Unexpected Element ... RequestElement, but expecting "none"
Is this due to the problem : http://issues.apache.org/activemq/browse/SM-749 One final question...where can I raise the jira? :) gnodet wrote: > > The badly generated is a known problem, but I don't think > a JIRA has been created yet. If you mind creating one ... > However, it should not affect the ability for the component to > process requests correctly. > When generating the pojo from the wsdl, does the wsdl > uses a doc/lit binding ? > > On 3/27/07, Ujval <[EMAIL PROTECTED]> wrote: >> >> >> Hi, >> >> I am trying to deploy a web service (starting from wsdl) in servicemix >> using >> jsr181 component. >> >> I generated server side classes from the wsdl using WsGen of XFire >> 1.2.2and >> then defined the property PojoClass in jsr181 to the implementation class >> generated by wsgen. >> >> I tried two cases. First, when I also provide my wsdl using the >> wsdlResource >> property, it generates a correct wsdl. Second, when I dont give the >> wsdlResource, it just generates some crappy wsdl with no schema and >> ill-formed elements. >> >> In the first case I tried invoking the service and to my surprise it >> doesnt >> even recognize the Request element present in the wsdl. A soap fault is >> returned saying...it's expecting none, but found the Request element. >> >> Is this a problem with the jsr181 component? I have seen similar posts in >> the forum but found no solution for the same. >> >> servicemix.xml: >> >> <sm:activationSpec> >> <sm:component> >> <jsr181:component> >> <jsr181:endpoints> >> <jsr181:endpoint pojoClass="aaa.xxx.AsdfImpl" >> service="tns:servicename" >> endpoint="serviceSOAP" >> typeMapping="jaxb2" >> annotations="jsr181" >> style="document" >> /> >> </jsr181:endpoints> >> </jsr181:component> >> </sm:component> >> </sm:activationSpec> >> >> <sm:activationSpec componentName="consumer"> >> <sm:component> >> <http:component> >> <http:endpoints> >> <http:endpoint >> service="tns:servicename" >> >> endpoint="serviceSOAP" >> role="consumer" >> locationURI=" >> http://localhost:8192/XXX/"; >> defaultMep=" >> http://www.w3.org/2004/08/wsdl/in-out"; >> soap="true" /> >> </http:endpoints> >> </http:component> >> </sm:component> >> </sm:activationSpec> >> >> >> Any help in this regard is appreciated. >> >> Thanks, >> Ujval >> >> P.S. : I am able to run the simple example of the jsr181 (found in the >> examples) without any issues. >> >> >> >> >> >> -- >> View this message in context: >> http://www.nabble.com/jsr181---problem-with-top-down-approach-tf3474454s12049.html#a9697101 >> Sent from the ServiceMix - User mailing list archive at Nabble.com. >> >> > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Architect, LogicBlaze (http://www.logicblaze.com/) > Blog: http://gnodet.blogspot.com/ > > -- View this message in context: http://www.nabble.com/jsr181---problem-with-top-down-approach-tf3474454s12049.html#a9698133 Sent from the ServiceMix - User mailing list archive at Nabble.com.
