I had a similar problem - needed to allow clients that
were accessing a web service in rpc/encoded to hit a
web service that would allow doc/literal also. I was
able to change the rpc/encoded wsdl into doc/literal
wsdl that acccepted the exact same soap messages. So
in the end both wsdls worked.
I generated the XFire service using the doc/literal
wsdl. I also served up a static wsdl using:
service.setWSDLWriter(new ResourceWSDL(wsdlUrl));
So the wsdl served to the client does not have to be
exactly what you generate your service with so long as
the SOAP message format is the same.
--- Jeff Pantazes <[EMAIL PROTECTED]> wrote:
> I am aware that the current version of xfire does
> not support Rpc/Encoded
> wsdls. However do any of the previous versions
> support it? I have a wsdl
> that I must write a web service for, unfortunately
> changing the wsdl and the
> client to support rpc/literal is not an option. :(
>
> When I set up xfire and just using the auto
> generated wsdl for rpc/literal
> it works wonderfully (hence I get object and it has
> data). When I change
> xfire to do rpc/encoded (still with the auto
> generated wsdl) the method is
> called and a non-null object is passed in, however
> the object has no data
> within it.
>
> example:
>
> myWebServiceMethod(MyObject ob)
> {
> String name = obj.getName(); //name is null when
> using rpc/encoded
> }
>
>
>
> Thanks,
>
> Jeff
>
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
