You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Andreas Pieber (JIRA)" <ji...@apache.org> on 2011/01/11 15:00:53 UTC
[jira] Created: (KARAF-380) Add .jar deployer autowrapping
non-bundle-jar files dropped to deploy folder
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.
[jira] Commented: (KARAF-380) Add .jar deployer autowrapping
non-bundle-jar files dropped to deploy folder
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985645#action_12985645 ]
Guillaume Nodet commented on KARAF-380:
---------------------------------------
Yeah, we definitely need to have an ordering based on the service ranking and make sure this wrap deployer has a very low one.
Note that ServiceReference are natively correctly ordered, so we should not have to use a custom comparator (but the logic may need to be refactored somehow).
> 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
> Assignee: Jean-Baptiste Onofré
>
> 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.
[jira] Commented: (KARAF-380) Add .jar deployer autowrapping
non-bundle-jar files dropped to deploy folder
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985650#action_12985650 ]
Guillaume Nodet commented on KARAF-380:
---------------------------------------
Unfortunately, this is in fileinstall issue ...
> 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
> Assignee: Jean-Baptiste Onofré
>
> 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.
[jira] Commented: (KARAF-380) Add .jar deployer autowrapping
non-bundle-jar files dropped to deploy folder
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12987463#action_12987463 ]
Guillaume Nodet commented on KARAF-380:
---------------------------------------
Added compuation of symbolic name + version.
Just need to document.
> 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
> Assignee: Jean-Baptiste Onofré
>
> 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.
[jira] Assigned: (KARAF-380) Add .jar deployer autowrapping
non-bundle-jar files dropped to deploy folder
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré reassigned KARAF-380:
------------------------------------------
Assignee: Jean-Baptiste Onofré
> 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
> Assignee: Jean-Baptiste Onofré
>
> 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.
[jira] Commented: (KARAF-380) Add .jar deployer autowrapping
non-bundle-jar files dropped to deploy folder
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12982658#action_12982658 ]
Jean-Baptiste Onofré commented on KARAF-380:
--------------------------------------------
I've commited a first very simple wrap deployer: revision 1059934.
I'm gonna make some enhancements especially around the Bundle-SymbolicName and Bundle-Version (getting from the MANIFEST or from the file name).
The BlueprintTranslator provides an extractNameVersionType() method. This method is copied and used in several Karaf projects (spring deployer, feature deployer, etc). So it should be in the utils bundle.
The first action is to move the extractNameVersionType() into utils.
> 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
> Assignee: Jean-Baptiste Onofré
>
> 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.
[jira] Commented: (KARAF-380) Add .jar deployer autowrapping
non-bundle-jar files dropped to deploy folder
Posted by "Andreas Pieber (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12981371#action_12981371 ]
Andreas Pieber commented on KARAF-380:
--------------------------------------
Well, actually it wasn't my idea but is a summarization from discussions on the mailinglist and the irc channel :)
@adding a my.osgi file: This will provide you with a possibility to change deployment params if it doesn't work on the fly ("autowrapping") as you like. At least it will certainly help you during complex jar -> to bundle processes (or speed up the process enormously) --> +1
> 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.
[jira] Commented: (KARAF-380) Add .jar deployer autowrapping
non-bundle-jar files dropped to deploy folder
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (KARAF-380) Add .jar deployer autowrapping
non-bundle-jar files dropped to deploy folder
Posted by "Achim Nierbeck (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12981475#action_12981475 ]
Achim Nierbeck commented on KARAF-380:
--------------------------------------
so the deployer has to take a look at the location of the jar to find the x.osgi file?
how about exploded jars? how would you handle this.
And another one, since file install is polling the directory it will always try to deploy the x.osgi file too,
which isn't bad but still another thread always running and trying with the same file over and over again.
I've seen this while debugging for an issue with the war deployer with the default README file.
> 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.
[jira] Commented: (KARAF-380) Add .jar deployer autowrapping
non-bundle-jar files dropped to deploy folder
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984586#action_12984586 ]
Jean-Baptiste Onofré commented on KARAF-380:
--------------------------------------------
Quick fix to handle only jar files: revision 1061649.
> 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
> Assignee: Jean-Baptiste Onofré
>
> 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.
[jira] Commented: (KARAF-380) Add .jar deployer autowrapping
non-bundle-jar files dropped to deploy folder
Posted by "Achim Nierbeck (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12981954#action_12981954 ]
Achim Nierbeck commented on KARAF-380:
--------------------------------------
you might take a look at the war-deployer of the pax-web project, it's the currently used deployer.
> 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
> Assignee: Jean-Baptiste Onofré
>
> 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.
[jira] [Closed] (KARAF-380) Add .jar deployer autowrapping
non-bundle-jar files dropped to deploy folder
Posted by "Jamie goodyear (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jamie goodyear closed KARAF-380.
--------------------------------
> 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
> Assignee: Jean-Baptiste Onofré
> Fix For: 2.2.0
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (KARAF-380) Add .jar deployer autowrapping
non-bundle-jar files dropped to deploy folder
Posted by "Achim Nierbeck (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985635#action_12985635 ]
Achim Nierbeck commented on KARAF-380:
--------------------------------------
Got another requirement :)
the way the jar is displayed should be done in a nicer way.
e.g. foo.jar should be rendered as foo(0) instead of opt_karaf_deploy_foo_jar (or similar)
The war deployer does that :) might take a look at it :)
> 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
> Assignee: Jean-Baptiste Onofré
>
> 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.
[jira] Commented: (KARAF-380) Add .jar deployer autowrapping
non-bundle-jar files dropped to deploy folder
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984579#action_12984579 ]
Jean-Baptiste Onofré commented on KARAF-380:
--------------------------------------------
I made a mistake in the wrap deployer: it should consider only the .jar deployment (not other files).
I'm gonna to fix it.
> 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
> Assignee: Jean-Baptiste Onofré
>
> 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.
[jira] Commented: (KARAF-380) Add .jar deployer autowrapping
non-bundle-jar files dropped to deploy folder
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985824#action_12985824 ]
Guillaume Nodet commented on KARAF-380:
---------------------------------------
Fixed the ordering issue.
> 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
> Assignee: Jean-Baptiste Onofré
>
> 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.
[jira] Commented: (KARAF-380) Add .jar deployer autowrapping
non-bundle-jar files dropped to deploy folder
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12981768#action_12981768 ]
Jean-Baptiste Onofré commented on KARAF-380:
--------------------------------------------
Indeed.
I'm gonna make a first deployer to simply wrap third party jar file.
> 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
> Assignee: Jean-Baptiste Onofré
>
> 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.
[jira] Commented: (KARAF-380) Add .jar deployer autowrapping
non-bundle-jar files dropped to deploy folder
Posted by "Achim Nierbeck (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985394#action_12985394 ]
Achim Nierbeck commented on KARAF-380:
--------------------------------------
There is still an issue regarding exploded jars (jardir) right now the web-deployer can't handle exploded wars anymore because the jar deployer kicks in before.
> 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
> Assignee: Jean-Baptiste Onofré
>
> 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.
[jira] Commented: (KARAF-380) Add .jar deployer autowrapping
non-bundle-jar files dropped to deploy folder
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986344#action_12986344 ]
Jean-Baptiste Onofré commented on KARAF-380:
--------------------------------------------
Thanks for the ordering issue.
I'm resuming the work on this JIRA.
> 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
> Assignee: Jean-Baptiste Onofré
>
> 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.
[jira] Resolved: (KARAF-380) Add .jar deployer autowrapping
non-bundle-jar files dropped to deploy folder
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet resolved KARAF-380.
-----------------------------------
Resolution: Fixed
Fix Version/s: 2.2.0
I think this one is done now.
> 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
> Assignee: Jean-Baptiste Onofré
> Fix For: 2.2.0
>
>
> 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.
[jira] Work started: (KARAF-380) Add .jar deployer autowrapping
non-bundle-jar files dropped to deploy folder
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on KARAF-380 started by Jean-Baptiste Onofré.
> 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
> Assignee: Jean-Baptiste Onofré
>
> 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.