[
https://issues.apache.org/jira/browse/FELIX-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved FELIX-2027.
------------------------------------
Resolution: Fixed
Committing to https://svn.apache.org/repos/asf/felix/trunk ...
M karaf/deployer/blueprint/pom.xml
M
karaf/deployer/blueprint/src/main/resources/OSGI-INF/blueprint/blueprint-deployer.xml
M karaf/deployer/features/pom.xml
M
karaf/deployer/features/src/main/java/org/apache/felix/karaf/deployer/features/FeatureDeploymentListener.java
M
karaf/deployer/features/src/main/resources/OSGI-INF/blueprint/features-deployer.xml
M karaf/deployer/spring/pom.xml
M
karaf/deployer/spring/src/main/resources/OSGI-INF/blueprint/spring-deployer.xml
Committed r905551
> The custom deployers leveraging url handlers must not be registered before
> the url handler is actually registered in the osgi framework
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: FELIX-2027
> URL: https://issues.apache.org/jira/browse/FELIX-2027
> Project: Felix
> Issue Type: Bug
> Components: Karaf
> Affects Versions: karaf-1.2.0
> Reporter: Guillaume Nodet
> Assignee: Guillaume Nodet
> Fix For: karaf-1.4.0
>
>
> We must make sure that the URL handler is ready to use when the custom
> fileisntall deployer is registered, else fileinstall can start using the
> deployer and lead to a failure if the url handler has not been fully
> registered with the framework. The reason is that the URL handler is
> registered in the same blueprint bundle.
> In order to improve reliability, add a reference to the url handler to the
> deployer.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
