Guillaume Yziquel created KARAF-2486:
----------------------------------------
Summary: No exported handler for manifest tag in blueprint xml
files
Key: KARAF-2486
URL: https://issues.apache.org/jira/browse/KARAF-2486
Project: Karaf
Issue Type: Bug
Components: karaf-osgi
Affects Versions: 2.3.0
Reporter: Guillaume Yziquel
Priority: Minor
Case 1: Take a blueprint xml file with a manifest tag. Deploy it in the deploy
folder or via an osgo:install blueprint:mvn: command. It works.
Case 2: Take the same blueprint xml file with a manifest tag. Use
maven-bundle-plugin to wrap it up in an osgi bundle. It hangs with a
GracePeriod status.
In the second case, it is waiting on an osgi service for the
http://karaf.apache.org/xmlns/deployer/blueprint/v1.0.0 namespace handler.
As this namespace handler is likely only used inside the karaf deployer, it is
not so surprising that it is local to the karaf deployer, and thus not handled
in case of deploying a vanilla bundle.
However, it would really be nice if we did not have to modify a blueprint xml
file depending on whether we are deploying via the deployer or deploying it
embedded in the OSGI-INF/blueprint folder of a bundle.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
