[jira] Commented: (FELIX-38) Improve URL Handlers to work when handler factories are already set

["Devajyoti Chakraborty (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FELIX-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12504396 ] 

Devajyoti Chakraborty commented on FELIX-38:
--------------------------------------------

I am trying to embedd Felix 0.8 into OC4j Container, while doing so, I keep getting the following error: -
==================================================================================
07/06/13 16:13:21 ERROR: Unable to start system bundle. (org.osgi.framework.Bund
leException: Unable to start system bundle.)
07/06/13 16:13:21 java.lang.Error: factory already defined
07/06/13 16:13:21       at java.net.URL.setURLStreamHandlerFactory(URL.java:1074
)
==================================================================================

I assume this is the same error being discussed in this forum. Since I have tried working with equinox and have successfully been able to run equinox in Jboss container, i was wondering if any solution / patch is available with the Felix 0.8 release?  

> Improve URL Handlers to work when handler factories are already set
> -------------------------------------------------------------------
>
>                 Key: FELIX-38
>                 URL: https://issues.apache.org/jira/browse/FELIX-38
>             Project: Felix
>          Issue Type: Improvement
>          Components: Framework
>    Affects Versions: 0.8.0
>            Reporter: Richard S. Hall
>            Assignee: Richard S. Hall
>            Priority: Minor
>             Fix For: 1.0.0
>
>         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.
-
You can reply to this email to add a comment to the issue online.