Re: exposing multiple classes as part of the same web service

[Tim K. (Gmane)]

Yeah, it would be nice to keep them separate, I've posted a while ago on 
the same topic. My concern is that I am not controlling what WS toolkit 
clients will use on the client side and these modules have the concept 
of a common session for all of them to work together, so I am not sure 
whether various toolkits will be able to play games on the client side 
with the session cookie (I have to do session tracking via HTTP session 
cookies rather than SOAP headers), setting it on the various stubs 
before it makes the calls. The easy way out is to put everything in one 
WSDL which will take care of the session sharing and then the client can 
decide to split them via wrapper classes on the client side if it's 
possible (we may even provide this code for Java clients that use Axis 
for example). It seems to me that this would provide the highest level 
of compatibility, am I right?

The other thing is that I don't know what extra resources I would need 
on the server side if I have 12 web services rather than 1 big one (in 
terms of additional objects that Axis may use internally to keep track 
and service the sessions for the deployed web services).

Tim
[EMAIL PROTECTED] wrote:
I would guess that these different interfaces and their implementations 
are separate for a reason. If so, why not keep the web services 
separate, for the same reasons, plus the additional reason that you 
don't end up with a huge, incomprehensible WSDL?

Incidentally, you don't have to create a combined interface. Axis isn't 
bothered with interfaces, it is concerned with implementations, since 
that is what is called by the engine (though Axis generates interfaces 
for client side code, with WSDL2Java). So, if you *have* to combine the 
services, just create an implementation of the different interfaces and 
route the calls as appropriate.

Tony
news <[EMAIL PROTECTED]> wrote on 20/12/2004 18:52:22:
 > Hi,
 >
 > Let's assume that I already have a few interfaces and their
 > implementation that follow all the web services rules and they are
 > suitable of being exposed via Axis the way they are.
 >
 > Is it possible for Axis to combine all these interfaces/classes into one
 > web service automatically or do I have to write one big interface that
 > extends all the existing interfaces and its implementation class to call
 >   thru to the existing implementations?
 >
 > Thank you,
 >
 > Tim
 >
 >