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
>
>
- exposing multiple classes as part of the same web servic... Tim K. (Gmane)
- Re: exposing multiple classes as part of the same w... tony . q . weddle
- Re: exposing multiple classes as part of the sa... Tim K. (Gmane)
