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
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
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
