Come on Srinath .. its ONE more line of code:
- create the repo
- create the config context using ConfigurationContextFactory
- now create the ServiceClient
I hardly see that being hard .. and its not a common case anyway. If you
have your own repo then its unlikely its something you use for exactly
one service client - so most likely you'll create your config from the
repo and re-use the config context.
I don't see the need to make ServiceClient more complex/flexible.
Sanjiva.
On Fri, 2006-02-24 at 11:46 -0500, Srinath Perera wrote:
> Thanks Glen !!
>
> > ServiceClient should definitely (IMO) have a way of providing a
> > Repository (i.e. an abstract repository API that only cares about the
> > Objects, not the XML) via the API. Then you can create a FileRepository
> > configured the way you want it, and pass that in:
> >
> > FileRepository repo = new FileRepository(myPath);
> > ServiceClient client = new ServiceClient(repo);
>
> yes, this exactly what I want to do !!
>
> But now ServiceClient(ConfigurationContext,AxisService) need user to
> create ConfigurationContext ,AxisService, add Operations to service
> ect .. which is hardly a easy way to override!
>
> > then of course I could also programatically do:
> >
> > CustomRepository repo = new CustomRepository();
> > repo.deployService("test", myClass);
> > repo.deployModule("addressing", addrModule);
> > ...
> > ServiceClient client = new ServiceClient(repo);
>
> :D cool
>
> Thanks
> Srinath
>
>
> --
> ============================
> Srinath Perera:
> http://www.cs.indiana.edu/~hperera/
> http://www.bloglines.com/blog/hemapani
