Hi, This is a good question. No, currently SA can't tell the difference if symbolic names are same.
A work around, if you build those bundles, you actually can specify the symbolic name yourself, to make different version bundles use different symbolic name. －－－－－－－－－－－－－ Freeman(Yue) Fang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://fusesource.com | http://www.redhat.com/ Twitter: freemanfang Blog: http://freemanfang.blogspot.com http://blog.sina.com.cn/u/1473905042 weibo: @Freeman小屋 On 2012-12-12, at 下午3:17, Tanvi wrote: > Hey Freeman, > > Thanks for quick help:) > > As per your suggestion, all shared JARs should not be added in SA/SUs but > should be deployed as separate bundles and classpath entries to be added in > SA/SUs. > > Consider a case, > My DAO, Delegate, Util projects are used by multiple SAs. One SA needs to > use version 1.0 of all, other needs version 2.0 of all. > As Symbolic name in MANIFEST.MF file does not contain version, it would > remain same though version is different. Classpath entry in 2 of the SAs > will remain same as it refers only symbolic name and doesnot have version in > it. > > How will each SA identify bundles of its own required versions if symbolic > name mentioned in both is same? > > Regards, > Tanvi > > > > -- > View this message in context: > http://servicemix.396122.n5.nabble.com/Class-cast-exception-while-sending-message-from-JBI-to-other-using-NMR-tp5715233p5715242.html > Sent from the ServiceMix - User mailing list archive at Nabble.com.
