Bernd Fondermann wrote:
Hi,
with the release of the OSGi extension to Spring[1], it seems to be
reasonably easy to turn any spring app into an OSGi deployment ('bundle').
I'd like to try and make the spring deployment OSGi-deployable this way.
In a first step, this would only mean 'deployable'. I would defer
exposing any interfaces as OSGi services or even splitting James into
multiple bundles.
I managed to hand-craft a bundle which could be deployed in Apache Felix
(which is our fellow OSGi container, as you probably know).
When it comes to activate our components, in our case it's starting to
get tricky though. It would be easy if we'd have a standard spring
deployment based on the typical spring-xml-config files. But...
We don't have standard. What we have is
a. a classic spring config (which is read by a standard
BeanDefinitionReader) with the basic components for mimicking Phoenix
behavior
_plus_
b. the original Avalon config file which is read by our _custom_
AvalonBeanDefinitionReader.
At startup, both are combined into the non-standard
AvalonApplicationContext.
Spring-osgi (opposed to Spring in a web-container) is not yet ready to
deal with custom ApplicationContexts (yet). This results in the fact I
see no easy way currently to boot our components.
Discussion about that is here:
http://groups.google.com/group/spring-osgi/browse_thread/thread/c0228e1a21760103
Bernd
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
