Re: Issue about karaf 2.3.3's deployment
Hi JB, I tried with you suggested, as below karaf@root> osgi:install wrap:file:tibjmsufo-5.1.2.jar Bundle ID: 220 karaf@root> headers 220 *wrap_file_tibjmsufo-5.1.2.jar (220) --- Manifest-Version = 1.0 Bnd-LastModified = 1390185491654 Tool = Bnd-0.0.357 Originally-Created-By = 1.5.0_10 (Sun Microsystems Inc.) Generated-By-Ops4j-Pax-From = wrap:file:tibjmsufo-5.1.2.jar Created-By = 1.6.0_37 (Sun Microsystems Inc.) Bundle-Name = wrap_file_tibjmsufo-5.1.2.jar Bundle-SymbolicName = wrap_file_tibjmsufo-5.1.2.jar Bundle-Version = 0 Bundle-ManifestVersion = 2 Import-Package = com.tibco.tibems.ufo;resolution:=optional, com.tibco.tibjms;resolution:=optional, javax.jms;resolution:=optional Export-Package = com.tibco.tibems.ufo;uses:="javax.jms,com.tibco.tibjms"* Apparently, it works fine. but the bundle version is wrong. If I deploy it under the deploy folder, the bundle version is also OK. *Why the bundle version is wrong?* -- View this message in context: http://karaf.922171.n3.nabble.com/Issue-about-karaf-2-3-3-s-deployment-tp4031037p4031186.html Sent from the Karaf - User mailing list archive at Nabble.com.
Re: Issue about karaf 2.3.3's deployment
Hi you can use: osgi:install wrap:file:... wrap: supports additional OSGi headers definition like Bundle-SymbolicName, etc that you can provide directly in the URL (with ?..&...) Regards JB On 01/15/2014 09:40 AM, simafengyun1984 wrote: Hi JB, I encountered an issue today. I have 5 third-party jars, but they are not the standard bundle files which have no bundle description information in the MANIFEST.MF. When I put them to the deploy folder. The 5 jar file will be installed and started in the karaf automatically and karaf will wrap them. I executed the command "headers" and it will show the bundle information( Actually these information is not in the MANIFEST.MF file), like below /karaf@root> headers 98 tibjmsufo (98) -- Manifest-Version = 1.0 Bnd-LastModified = 1389772893126 Tool = Bnd-0.0.357 Originally-Created-By = 1.5.0_10 (Sun Microsystems Inc.) Generated-By-Ops4j-Pax-From = wrap:file:/opt/gravity/apache-karaf-2.3.3/deploy/tibjmsufo-5.1.2.jar$Bundle-SymbolicName=tibjmsufo&Bundle-Version=5.1.2 Created-By = 1.6.0_31 (Sun Microsystems Inc.) Bundle-Name = tibjmsufo Bundle-SymbolicName = tibjmsufo Bundle-Version = 5.1.2 Bundle-ManifestVersion = 2 Import-Package = com.tibco.tibems.ufo;resolution:=optional, com.tibco.tibjms;resolution:=optional, javax.jms;resolution:=optional Export-Package = com.tibco.tibems.ufo;uses:="javax.jms,com.tibco.tibjms"/ Apparently the karaf wrap the jars to standard bundles automaticatlly In this case, my project works file in the karaf. But when I put the jar files out side the deploy folder and executed the command like "install file:tibjms-6.1.jar". I failed to start the bundles. I executed the command "headers", it shows no bundle information, just some useless information got from the MANIFEST.MF, as below /karaf@root> headers 92 Bundle 92 - Manifest-Version = 1.0 Created-By = 1.5.0_10 (Sun Microsystems Inc.)/ *My question: How to make the karaf wrap the non-standard bundle to standard bundles when use the command like "install file:tibjms-6.1.jar"? * -- View this message in context: http://karaf.922171.n3.nabble.com/Issue-about-karaf-2-3-3-s-deployment-tp4031037.html Sent from the Karaf - User mailing list archive at Nabble.com. -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
FW: Issue about karaf 2.3.3's deployment
use the following command: features:install wrap:file:tibjms-6.1.jar Best Rgds, Tom -Original Message- From: simafengyun1984 [mailto:yifeng@citi.com] Sent: Wednesday, January 15, 2014 4:41 PM To: user@karaf.apache.org Subject: Issue about karaf 2.3.3's deployment Hi JB, I encountered an issue today. I have 5 third-party jars, but they are not the standard bundle files which have no bundle description information in the MANIFEST.MF. When I put them to the deploy folder. The 5 jar file will be installed and started in the karaf automatically and karaf will wrap them. I executed the command "headers" and it will show the bundle information( Actually these information is not in the MANIFEST.MF file), like below /karaf@root> headers 98 tibjmsufo (98) -- Manifest-Version = 1.0 Bnd-LastModified = 1389772893126 Tool = Bnd-0.0.357 Originally-Created-By = 1.5.0_10 (Sun Microsystems Inc.) Generated-By-Ops4j-Pax-From = wrap:file:/opt/gravity/apache-karaf-2.3.3/deploy/tibjmsufo-5.1.2.jar$Bundle- SymbolicName=tibjmsufo&Bundle-Version=5.1.2 Created-By = 1.6.0_31 (Sun Microsystems Inc.) Bundle-Name = tibjmsufo Bundle-SymbolicName = tibjmsufo Bundle-Version = 5.1.2 Bundle-ManifestVersion = 2 Import-Package = com.tibco.tibems.ufo;resolution:=optional, com.tibco.tibjms;resolution:=optional, javax.jms;resolution:=optional Export-Package = com.tibco.tibems.ufo;uses:="javax.jms,com.tibco.tibjms"/ Apparently the karaf wrap the jars to standard bundles automaticatlly In this case, my project works file in the karaf. But when I put the jar files out side the deploy folder and executed the command like "install file:tibjms-6.1.jar". I failed to start the bundles. I executed the command "headers", it shows no bundle information, just some useless information got from the MANIFEST.MF, as below /karaf@root> headers 92 Bundle 92 - Manifest-Version = 1.0 Created-By = 1.5.0_10 (Sun Microsystems Inc.)/ *My question: How to make the karaf wrap the non-standard bundle to standard bundles when use the command like "install file:tibjms-6.1.jar"? * -- View this message in context: http://karaf.922171.n3.nabble.com/Issue-about-karaf-2-3-3-s-deployment-tp403 1037.html Sent from the Karaf - User mailing list archive at Nabble.com.
Issue about karaf 2.3.3's deployment
Hi JB, I encountered an issue today. I have 5 third-party jars, but they are not the standard bundle files which have no bundle description information in the MANIFEST.MF. When I put them to the deploy folder. The 5 jar file will be installed and started in the karaf automatically and karaf will wrap them. I executed the command "headers" and it will show the bundle information( Actually these information is not in the MANIFEST.MF file), like below /karaf@root> headers 98 tibjmsufo (98) -- Manifest-Version = 1.0 Bnd-LastModified = 1389772893126 Tool = Bnd-0.0.357 Originally-Created-By = 1.5.0_10 (Sun Microsystems Inc.) Generated-By-Ops4j-Pax-From = wrap:file:/opt/gravity/apache-karaf-2.3.3/deploy/tibjmsufo-5.1.2.jar$Bundle-SymbolicName=tibjmsufo&Bundle-Version=5.1.2 Created-By = 1.6.0_31 (Sun Microsystems Inc.) Bundle-Name = tibjmsufo Bundle-SymbolicName = tibjmsufo Bundle-Version = 5.1.2 Bundle-ManifestVersion = 2 Import-Package = com.tibco.tibems.ufo;resolution:=optional, com.tibco.tibjms;resolution:=optional, javax.jms;resolution:=optional Export-Package = com.tibco.tibems.ufo;uses:="javax.jms,com.tibco.tibjms"/ Apparently the karaf wrap the jars to standard bundles automaticatlly In this case, my project works file in the karaf. But when I put the jar files out side the deploy folder and executed the command like "install file:tibjms-6.1.jar". I failed to start the bundles. I executed the command "headers", it shows no bundle information, just some useless information got from the MANIFEST.MF, as below /karaf@root> headers 92 Bundle 92 - Manifest-Version = 1.0 Created-By = 1.5.0_10 (Sun Microsystems Inc.)/ *My question: How to make the karaf wrap the non-standard bundle to standard bundles when use the command like "install file:tibjms-6.1.jar"? * -- View this message in context: http://karaf.922171.n3.nabble.com/Issue-about-karaf-2-3-3-s-deployment-tp4031037.html Sent from the Karaf - User mailing list archive at Nabble.com.
