[
https://issues.apache.org/activemq/browse/SMX4-579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61248#action_61248
]
Geert Schuring edited comment on SMX4-579 at 8/18/10 4:31 AM:
--------------------------------------------------------------
This is why every bundle should have package-import statements covering all
packages it exports. That way, if 2 bundles offer the same code (which happens
frequently) the OSGi classloaders make sure that only 1 version is used
throughout the JVM.
This is the maven-bundle-plugin' s default behaviour. See
http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html
Extract:
"<Import-Package> is assumed to be "*", which imports everything referred to by
the bundle content, but not contained in the bundle.
Any exported packages are also imported by default, to ensure a consistent
class space."
was (Author: cathodion):
This is why every bundle should have package-import statements covering its
own packages. That way, if 2 bundles offer the same code (which happens
frequently) the OSGi classloaders make sure that only 1 version is used
throughout the JVM.
> extract common used classes for itests
> --------------------------------------
>
> Key: SMX4-579
> URL: https://issues.apache.org/activemq/browse/SMX4-579
> Project: ServiceMix 4
> Issue Type: Improvement
> Reporter: Freeman Fang
> Assignee: Freeman Fang
> Fix For: 4.4.0
>
>
> this avoid put same classes in different bundles, which can cause
> ClassCastException
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
