Hi Tony;
Sorry for late reply;
Service client has an API which can take WSDL and create e client for
that , and after that you can invoke the service using the created
client, But you have to create the OMElemnt and pass that to the
whatever method you are going to use.
public ServiceClient(ConfigurationContext configContext, URL wsdlURL,
QName wsdlServiceName, String portName) throws
AxisFault {}
Tony Dean wrote:
>Hi,
>
>I will preface this saying that I have not done much client development...
>spending much of my time developing web services themselves. Now, I have need
>to develop a client that can take an arbitrary wsdl on the fly and generate
>SOAP requests irregardless of the web service endpoint style (rpc/document,
>literal/encoded). The SOAP envelope request will need to be generated at
>runtime so that they process is truly dynamic. I was thinking of using
>something like wsdl4j to interpret the wsdl and then generate the payload
>accordingly. Is this the right approach? In your client samples you
>basically have a ServiceClient that can send OMElement structure in varying
>MEPs. Is there an API that I can use to tell you for instance that this
>request is an rpc request with such and such parameters. Or is this left up
>to the programmer to encode in the OMElement structure? Just looking for some
>insight and direction
>
>
>Thanks for your time.
>
>Tony Dean
>SAS Institute Inc.
>919.531.6704
>[EMAIL PROTECTED]
>
>SAS... The Power to Know
>http://www.sas.com
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
>
--
Thanks,
Deepal
................................................................
~Future is Open~
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
