This is acceptable as long as we can separate it as another way to wire the server together. It cannot impose specifics on the components themselves. This way there is no direct dependence on the wiring technology be it Spring, EMF or OSGi.
One thing that needs to be voted on is whether it is acceptable for components to receive configuration data from a general context object. WIth a EMF based approach the server would first load server.xml, instantiating all the Beans modeled in apacheds-xbean-spring.xsd. If you follow the tutorial / trace I sent out earlier, you'll see how there are generated. As EMF loads server.xml it creates and binds server.xml to instances of these classes. These instances would then have to be made available to other components via a server context object. So the server startup process would be something like this:
- Load server.xml
- Get root configuration object from EMF Resource
(Metaphor for server.xml)
and place it on the server context
- Create all other server components, providing them with a reference
to the server context
So the question is "Is this acceptable?".