Hi,
You make a good point in suggesting why this method should stay; the drawback is that in general in WSIF we try to avoid any public API calls that tie the client code to a particular provider. In this case, your client code would have to cast the WSIFOperation used for invocation to WSIFOperation_ApacheAxis to make use of this method.
An alternative is to defer creation of the WSIFService until you have received the WSDL with the dynamic endpoint (or you can programmatically create a service definition with the dynamic endpoint using the code that Alek provided a link to below). Once you have that dynamically created definition, you can create the WSIFService, get the port, the operation and then perform the invocation.
Nirmal.
| "Ofer Baranes" <[EMAIL PROTECTED]>
09/27/2004 11:07 AM
|
To: <[EMAIL PROTECTED]> cc: Subject: RE: dynamically change wsdl service location |
Its seems ok , but the javadoc on WSIFPort_ApacheAxis.setEndPoint()
Indicate that the method is deprecated , and add 'should anyone be
calling this?' , I think it should stay since wsdl should be 'metadata'
and the endpoint is a runtime parameter which should not hardly bind to
the wsdl.
-----Original Message-----
From: Aleksander Slominski [mailto:[EMAIL PROTECTED]
Sent: Sunday, September 26, 2004 6:07 PM
To: [EMAIL PROTECTED]
Subject: Re: dynamically change wsdl service location
Ofer Baranes wrote:
> Can I make WSIF load a wsdl ,ignore it's 'service location',
>
> and on runtime set a location to the service ?
>
i am not sure what you mean by "on runtime" but you can load WSDL and
then modify wsdl:service/soap:[EMAIL PROTECTED] using WSDL4J.
for example:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg00362.html
is this what you want to do?
alek
> That
>
> way, one can supply wsdl to clients without a specific location.
>
>
>
>
>
--
The best way to predict the future is to invent it - Alan Kay
