Hi, dynamic-import is a standard manifest header, just add your required packages to the Dynamic-Importpackage manifest entry [1].
regards, Achim [1] - http://wiki.osgi.org/wiki/DynamicImport-Package 2014-09-25 9:39 GMT+02:00 Jens J Parappallil <[email protected]>: > Hi Achim, > > > > Thanks for the reply, > > > > Indeed I would be able to narrow down the packages, In karaf after > specifying the Dynamic-Import list also it is not getting enabled , using > the command “dynamic-import” it is getting enabled . This is a manual > process which I want to skip is there a way in karaf to automate this ? > > > > Regards > > Jens > > > > *From:* Achim Nierbeck [mailto:[email protected]] > *Sent:* 25 September 2014 12:44 > *To:* [email protected] > *Subject:* Re: Dynamic Import usage > > > > This is one of the rare cases where a dynamic Import is usable and build > for. > > But if you are able to narrow down the dynamic pattern to a certain > package level, > > for example com.mybusiness.serializable.objects.pattern.* you can make > sure you don't dynamically import the whole universe :) > > > > regards, Achim > > > > > > 2014-09-25 8:46 GMT+02:00 Jens J Parappallil <[email protected] > >: > > Hi , > > > > I have this following scenario > > > > 1. Bundle 1 : Weblogic jms connector bundle – this bundle registers > a camel jms component for weblogic server > > 2. Bundle 2 : camel route which uses this component > > 3. Bundle 3 : bundle containing the specific JMS Object message > type classes > > > > When an Object message is put into the queue , camel route goes to > deserialize the Object message which causes a ClassNotFoundException for > the JMS Object type classes . The problem is I don`t know what object > classes > > Would be placed in the queue hence can`t put the import-package in the > connector bundle . The type classes has be loaded dynamically by the > connector , what could be best approach to deal with scenario ? > > > > Thanks > > Jens > > > > > > DISCLAIMER: "The information in this e-mail and any attachment is > intended only for the person to whom it is addressed and may contain > confidential and/or privileged material. If you have received this e-mail > in error, kindly contact the sender and destroy all copies of the original > communication. IBS makes no warranty, express or implied, nor guarantees > the accuracy, adequacy or completeness of the information contained in this > email or any attachment and is not liable for any errors, defects, > omissions, viruses or for resultant loss or damage, if any, direct or > indirect." > > > > > > -- > > > Apache Member > > Apache Karaf <http://karaf.apache.org/> Committer & PMC > OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & > Project Lead > blog <http://notizblog.nierbeck.de/> > > > > Software Architect / Project Manager / Scrum Master > > > > > DISCLAIMER: "The information in this e-mail and any attachment is > intended only for the person to whom it is addressed and may contain > confidential and/or privileged material. If you have received this e-mail > in error, kindly contact the sender and destroy all copies of the original > communication. IBS makes no warranty, express or implied, nor guarantees > the accuracy, adequacy or completeness of the information contained in this > email or any attachment and is not liable for any errors, defects, > omissions, viruses or for resultant loss or damage, if any, direct or > indirect." > -- Apache Member Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead blog <http://notizblog.nierbeck.de/> Software Architect / Project Manager / Scrum Master
