[jira] Commented: (FELIX-756) Allow URLStreamHandler services to override built-in handlers.

["Pierre De Rop (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FELIX-756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641332#action_12641332 ] 

Pierre De Rop commented on FELIX-756:
-------------------------------------

Here are our use case: we have our http container bundle which provides an URLStreamHandlers service for protocol http/https.
Hence, when an http application (WAR) uses the jdk java.net.HttpURLConnection, our http container is able to take control over the
protocol and sockets (using URLStreamHandler service).

As you suggested, we could provide some classes in the classpath of the jvm (with java.protocol.handler.pkgs properties).
but this is a big deal for us because we have to expose in the classpath some classes from our http container bundle (and from other dependent bundles).
in other words, it's not easy for us to "unbundle-ize" our http container quickly.

On the other hand, I noticed that there is a property in Felix called
felix.strict.osgi: What is exactly the impact of setting this property to false ?

Would it be acceptable/possible, when this property is set to false, to
enable the http/https protocols for URLStreamHandler service ?


> Allow URLStreamHandler services to override built-in handlers. 
> ---------------------------------------------------------------
>
>                 Key: FELIX-756
>                 URL: https://issues.apache.org/jira/browse/FELIX-756
>             Project: Felix
>          Issue Type: Improvement
>          Components: Framework
>    Affects Versions: felix-1.2.2
>            Reporter: Karl Pauls
>            Assignee: Karl Pauls
>
> In certain cases it might be desirable to override built-in URLStreamHandlers with services provided by bundles. As of now, the spec doesn't allow this (see 11.3.2 ff) but it might in the future. Furthermore, it looks like other implementations are less strict on this issue as we are. For now, the best one can do is to put handlers in the classpath of the framework and make them available via the java.protocol.handler.pkgs properties. This way, one can override the built-in handlers but needs control over the jvm (which is not the best solution). 
> It should be possible to add an option to felix that will register handlers that proxy the built-in ones but prefer registered URLStreamHandler services if there is one available for a given schema. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.