I did not get your question: Axis is a development/run-time set of libraries, it is not a management tool ( as I recall). If an ESB contains an Axis module in certain version and your service (built with Axis) uses another Axis version, it might be a problem, I guess....
- Michael ----- Original Message ---- From: htshozawa <[EMAIL PROTECTED]> To: [email protected] Sent: Tuesday, June 24, 2008 10:45:59 PM Subject: [service-orientated-architecture] ESB/Intermediary in SOA (was Data services (was Re: Definition of SOA)) Just to make sure that we don't get into a loop, if I make a service available using Axis, does Axis manage every service version? What if a ESB contains an Axis module? H.Ozawa --- In service-orientated- architecture@ yahoogroups. com, Michael Poulin <[EMAIL PROTECTED] .> wrote: > >Now, if ESB acts as a service of its own, the consumer has to contract with ESB. It would be no problem here unless ESB magically represents service's functionality and RWE, and does it for every service version. Have you heard about such ESBs? Is it realistic to assume such creature at all? (For every service...?)
