Hi devs,
I'm currently about to refactor the Apache ODE OSGi stuff and wanted to
use the ManagedService from Axis2 for this.
Apparently there is no way to configure the service as it hardcodes a
reference to some internal axis2.xml which is then used for axis2
configuration.
So what I thought would be the right way of doing ManagedService stuff
here is to turn the current ManagedService
(OSGiConfigurationContextFactory) into a ManagedServiceFactory and
provide the ability to configure a new service instance using a given
Dictionary (of course this must fail in case someone tries to configure
two instances for the same HOST/PORT/CONTEXTPATH configuration).
So I think I might still use the internal axis2.xml for the defaults,
but make all configuration options available for the ConfigAdmin stuff.
Also in an OSGi service world it doesn't really make sense to create
some default ManagedService with no deployed services like it is
currently done using the Activator.
The way I would like this to change is that the Axis2 OSGi just provides
a ManagedServiceFactory that can be used to consume configured
ManagedServices from other services.
So the Apache ODE just has to retrieve a ManagedService instance with
its own configuration (ode-axis2 integration layer) which would also be
much more compliant to the standard OSGi services model, I think.
Does that sound mean to you?
Cheers,
CHaoZ
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
