Do you have a working prototype of your suggestion? I’ve read through your other thoughts on the Apache site and I think you’ve got some wonderful ideas.
In general, the lack of this functionality is a major problem with the IvyDE implementation and may be a showstopper for us, unless a comprehensive solution is available.
Thanks Andrei. I need to update this blog entry based on the feedback I got from the IvyDE mailing lists however I’m most of the way through implementing:
A type filter in IvyDE for JNI.
Populating the -Djava.library.path automatically from resolved artifacts in the type filter.
I’ve been quite busy at work, however I hope to have something working over the weekend. I’ll then feed this back to IvyDE and will ping you when I have something for you to try.
It defines a service-based approach for registering URL handlers in a modular, dynamic application. The basic idea is that you can register an implementation of URLStreamHandlerService with the OSGi service registry – the various service implementations are then discovered by the real (singleton) URLStreamHandler that’s registered by the OSGi framework. The framework handler is responsible for sending incoming requests to the right handler service.
Of course, there are some wrinkles (mostly when embedding frameworks inside other containers) but most OSGi frameworks can also support this by using reflection to chain to existing handler factories.
Hi Jeff,
Do you have a working prototype of your suggestion? I’ve read through your other thoughts on the Apache site and I think you’ve got some wonderful ideas.
In general, the lack of this functionality is a major problem with the IvyDE implementation and may be a showstopper for us, unless a comprehensive solution is available.
Any feedback would be greatly appreciated.
thanks
andrei
Thanks Andrei. I need to update this blog entry based on the feedback I got from the IvyDE mailing lists however I’m most of the way through implementing:
I’ve been quite busy at work, however I hope to have something working over the weekend. I’ll then feed this back to IvyDE and will ping you when I have something for you to try.
Jeff
You might want to look at the URL Handlers Service (chapter 11 of the OSGi core specification http://www.osgi.org/download/r4v42/r4.core.pdf)
It defines a service-based approach for registering URL handlers in a modular, dynamic application. The basic idea is that you can register an implementation of URLStreamHandlerService with the OSGi service registry – the various service implementations are then discovered by the real (singleton) URLStreamHandler that’s registered by the OSGi framework. The framework handler is responsible for sending incoming requests to the right handler service.
You can find a concrete example over at http://wiki.ops4j.org/display/paxurl/Pax+URL which also works in a standard Java environment, except without the dynamic part.
Of course, there are some wrinkles (mostly when embedding frameworks inside other containers) but most OSGi frameworks can also support this by using reflection to chain to existing handler factories.
Stuart, thanks for this, I was not fully aware of how OSGI works around the various issues and Chapter 11 does a good job at explaining it.