It depends what style/use Apache Soap is using. Remember that XFire
doesn't support RPC/Encoding.
On 7/27/07, Stephen Schaub <[EMAIL PROTECTED]> wrote:
> I have a legacy soap client written using Apache Soap that I am
> considering converting to XFire, since we're using XFire for most of
> our current Soap work. The problem is that I'm not a Soap expert, and
> I don't have the wsdl for the service the client talks to. I looked
> through the XFire API and user manual to try to determine how to map
> the calls, but am lost.
>
> Here's a short fragment from the existing Apache soap client code:
>
> ...
> Call call = new Call();
> call.setEncodingStyleURI(Constants.NS_URI_SOAP_ENC);
> call.setTargetObjectURI(targetObjectURI);
> Vector<Parameter> params = new Vector<Parameter>();
> params.addElement(new Parameter("username", String.class, username,
> Constants.NS_URI_SOAP_ENC));
> params.addElement(new Parameter("password", String.class, username,
> Constants.NS_URI_SOAP_ENC));
> call.setParams(params);
> Response resp = call.invoke(url, soapActionURI);
> ...
>
> I would appreciate feedback on whether XFire has a "manual client SOAP
> call" API that I can translate this to, or whether I would have to
> focus my efforts on writing a WSDL and have XFire generate client
> classes.
>
> --
> Stephen Schaub
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
--
-----
When one of our products stops working, we'll blame another vendor
within 24 hours.
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
