is the method used to call a web service operation good.?
thnaks.
lmk wrote:
>
> helloo,
>
> the code below describe how i call the web service, i remark that many
> Call objects are created and still loaded on the server session..
>
> i look for a design pattern to manage this objects. like a connection
> pool, what's the judicous solution?.
>
> //URL endpointURL = new URL(url);
> URL endpointURL = new URL(urlIAPP + "urn:myurn");
> String encodingStyleURI = Constants.NS_URI_SOAP_ENC;
>
> /*call web service*/
> Call call = new Call();
> call.setTargetObjectURI("urn:myService");
> call.setMethodName("getMethode");
> call.setEncodingStyleURI(encodingStyleURI);
>
>
> SOAPHTTPConnection hc = new SOAPHTTPConnection();
> hc.set..
> hc.set..
> call.setSOAPTransport(hc);
>
> call.invike() ...
> ------------------------------------------------------------
>
> thanks!
>
>
--
View this message in context:
http://www.nabble.com/-axis-1.3--how-to-manage-Call-objects-tf4231327.html#a12054354
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
