On 04/09/2012 20:45, Daniel Kulp wrote:
Not at this time, no. The major part of the problem involves the entire "class
loading" issue in OSGi. If you stick a class name in the config file, we likely
wouldn't be able to load it anyway since the CXF bundles wouldn't be importing the
package of the handler. Christian and I tossed around some ideas of having an OSGi
service name or something stuck in the config file and we grab the handler from the OSGi
service registry that way, but that would require a little more work in CXF that we
haven't had time for.
I'd certainly welcome any patches (likely to the above mentioned class as a
starting point) to get that working.
Dan
One option would be to define a CXF Jetty Handler Factory OSGi Service,
then the config file would just have to provide references to existing
services.
It's a bit irritating that Jetty handlers (though understandable) can
only be used in one context, so you can't just have the handler as a
service - and the factory would need some way to pass arguments to the
factory (we've found that all our handlers actually need some
configuration that is specific to the port they are handling).
That's essentially what we've done, but it's not generic and it wouldn't
be very easy to make it so :(
Jim
