> Srinath, it looks like you added a new constructor to ServiceClient: > > ServiceClient(ConfigurationContext configContext, > WSDLDescription wsdldesc, > QName wsdlServiceName, String portName) > > First of all, when making client API changes please send a note to the > list to discuss it a bit please
I did asked.. search archives for the mail "[Axis2]new constructor for Service Client". No body answered. So I just executed lazy census > I'd like to remove this constructor. Here are the reasons: > > - we already have support for the basic need of this scenario: read a > WSDL and execute off of that (the constructor that takes a URL instead > of a WSDLDescription) > > - I agree this is a useful feature (a BPEL runtime for example will read > the WSDLs and execute without reloading them), however doing this > exposes the WOM APIs to the client in a very direct manner. WOM is meant > as a temp thing until Woden comes along and is ready to service our WSDL > needs. If we expose the WSDLDescription class on the clinet API then > we've exposed WOM directly to users and have lost the opportunity to try > to replace the WOM later. We took quite an effort to pull that out of > AxisService etc. and I'd rather keep it that way to retain our future > freedom of action. > > What do you think Srinath? Can you live without this until we get the > Woden side sorted out? I accepted the reasons! Just to tell bit more on the use cases, the primary user of the dynamic invocation is work flow composers/ BPEL engines (they need 100% dynamic invocations). To handle data binding among other things they need wsdl info. If do not have that constructor or a get method for WSDL description engine have to parse the WSDL twice. 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. It seems wooden will take time, if it is another year .. it is almost ever for Axis2. My gut feeling is fate of Axis2 will be decided by that time. 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 trust you decision on this :), your call Srinath -- ============================ Srinath Perera: http://www.cs.indiana.edu/~hperera/ http://www.bloglines.com/blog/hemapani
