Scope
The scope of Antidoto is to provide an overall architecture guideline for the development of next generation, modular, enterprise java applications. Antidoto is not another "framework by restriction".
In the modern Java EE software development, the software architect regained the freedom of choice how to compose building parts, which technologies and which component models to use.
What antidoto is not
Antidoto is not...
... an OSGi solution and never will be.
If you need something with separate classloaders per subsystem, different versions of subsystem loaded, turning on and off subsystems, etc, then have a look at Equinox or other plugin architecture:
Links:
... an ESB solution and never will be.
Subsystems in Antidoto are meant to be loaded in the same scope as the system itself - from this point of view it is not a distribution solution.
Of course it is possible to load subsystems into a server runtime and expose services - if all you need simple remoting, spring remoting might do the magic (and does not conflict with Antidoto anyhow).
If you need a full blown ESB with service orchestration and more, that you are definitely looking at the wrong place.
Links: