On Sat, 2006-02-25 at 08:27 -0500, Srinath Perera wrote:
>
> Personally I can live without that constructor by creating may own
> ServiceClient Class (Even though I do not believe in private code like
> that). My concern is normal users, I know for a fact Taverna guys are
> trying to migrate to Axis2. What can they do, they had to parse the
> WSDL twice.
How about the following: add a new constructor to AxisService as
follows:
AxisService (URL wsdlURL, QName wsdlServiceName, String portName)
This can have the logic for reading the WSDL and creating a properly
configured AxisService (including all the policies at the right places).
Module engagement would have t happen in the context of a
ConfigurationContext object I believe.
Users can then create an AxisService and reuse it in any number of
ServiceClients using new ServiceClient (configContext, axisService).
In fact, once we have that, we can either (1) remove the ServiceClient
constructor which takes a WSDL URL, or (2) do its implementation as
this (configContext, new AxisService (...));
(I'd prefer to remove the constructor but I recognize I may be in the
minority in not liking choices in APIs.)
> If I could do the constructor on wsdl4j does it help (I have to make
> time to do that). And please instruct me what I used for policy impl
> .. WOM or wsdl4j. It seems WOM based utilities are already written.
I don't understand this comment - one more try please.
Sanjiva.
