[
https://issues.apache.org/jira/browse/KARAF-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12981324#action_12981324
]
Jean-Baptiste Onofré commented on KARAF-380:
--------------------------------------------
It's a good idea Andreas.
The PAX URL wrap: protocol provides the possibility to define OSGi statement in
the URI (such as the Bundle-SymbolicName, etc).
What do you think to add a .osgi file near the .jar file describing the OSGi
statements, like:
my.jar
my.osgi
where my.osgi contains:
Bundle-SymbolicName:
Bundle-Version:
etc ?
> Add .jar deployer autowrapping non-bundle-jar files dropped to deploy folder
> ----------------------------------------------------------------------------
>
> Key: KARAF-380
> URL: https://issues.apache.org/jira/browse/KARAF-380
> Project: Karaf
> Issue Type: New Feature
> Reporter: Andreas Pieber
>
> See http://mail-archives.apache.org/mod_mbox/karaf-dev/201101.mbox/browser
> for full discussion; short summary:
> My concern is to deploy clients JARs like by example JARS used by project
> Apache Hadoop
> If we detect a file in the deploy/ directory with the extension '.jar', AND
> the JAR's manifest does NOT contain any OSGi headers, THEN we assume that
> it's a plain-old-jar, and perform an auto-wrap.
> Using the OSGi ranking attribute on services should be sufficient in order to
> keep them ordered.
> And checking the 'jar' extension would clearly remove most of the bad
> situations for that case.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
