Sanjiva Weerawarana wrote:
On Fri, 2006-02-24 at 19:15 -0500, Srinath Perera wrote:
If we had constructor
public ServiceClient(ConfigurationContext configContext) throws AxisFault
Note that this idea is generally nonsensical: you want a client for a
service but don't say for what service. However, we do have the simplest
level of that auto supported already thru the no args constructor and
the approach indicated below.
that would have been true, but what we have is
public ServiceClient(ConfigurationContext configContext,
AxisService axisService) throws AxisFault
If you really want to use the simplest ServiceClient API (where we auto
create a dumb service underneath) then you can still do that .. pass
null as the 2nd arg. So we already have the capability you're looking
for.
I'm still not convinced your scenario is very common: the user is
advanced enough to create their own repo etc., but only wants to use the
dumb anonymous service? Doesn't compute for me. But hey, its
supported :).
I should create a repository, then a AxisService, add the operations
and then only call constructor. I can do that, but a new uesr would
not get it that easily. Can we add the first costructor?
Look at this way: why do I have to go to the effort of creating all the
(many) service declarations when all I want is to send XML documents to
a URL I've chosen? Its pretty painful setting up a serviceclient by hand.
