[ http://issues.apache.org/jira/browse/FELIX-38?page=all ]

Felix Meschberger updated FELIX-38:
-----------------------------------

    Attachment: FELIX-38.diff.gz

Attaching a complete reimplementation of the URLHandlers class (which is 
dropped and replaced by the now distinct URLHandlersURLStreamHandlerFactory and 
URLHandlersContentHandlerFactory classes).

These new classes together with a common abstract base class 
URLHandlersFactoryChain implement the new and improved registration, 
unregistration and multiplexing mechanism. This new mechanism is heavily 
reflection-based to circumvent class loader issues.

The registration part of these new classes is influenced by the solution of 
Eclipse/Equinox (see above mentioned bug). I took note of this fact in the 
class comments to the factory classes. Is this enough action to take here or is 
it required to further investigate whether this code is ok to submitted to 
Apache Felix in this manner ?

> Improve URL Handlers to work when handler factories are already set
> -------------------------------------------------------------------
>
>                 Key: FELIX-38
>                 URL: http://issues.apache.org/jira/browse/FELIX-38
>             Project: Felix
>          Issue Type: Improvement
>          Components: Framework
>            Reporter: Richard S. Hall
>            Priority: Minor
>         Attachments: FELIX-38.diff.gz
>
>
> The current implementation of URL Handlers expects to be able to set the 
> stream and content handler factories, which can only be set once per JVM. It 
> is possible that a framework instance might not be able to set these 
> factories if it is embedded inside of another application that has already 
> set them. It might be worthwhile to implement a workaround like the one 
> described here:
>     https://bugs.eclipse.org/bugs/show_bug.cgi?id=107909
> In short, it uses reflection to push the framework's factory handlers into 
> the runtime if they are already set and then delegates to them.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to