Hi,
Is it possible you have a package import statement for
"com.flytecomm.noaa_atom_feed_consumer" in the maven bundle-plugin of your
pom.
Also, do you have another bundle(s) exporting this class/package as well.
OSGi tends to look outside via the manifest for the package before looking
within (i.e internally) to resolve packages. If there are multiple such
copies of the same package in different bundles, you might want to in the
maven-bundle-plugin's import packages add the following entry. This will
force the bundle to resolve the package internally without external
interference.
<plugin>
<groupId>org.apache.felix</groupId>
<artifactId>maven-bundle-plugin</artifactId>
<version>${maven-bundle-plugin.version}</version>
<extensions>true</extensions>
<configuration>
<instructions>
<Bundle-SymbolicName>${project.artifactId}</Bundle-SymbolicName>
<Import-Package>
*,
!com.flytecomm.noaa_atom_feed_consumer,
...
</Import-Package>
</instructions>
</configuration>
</plugin>
Hope this helps...
Cheers,
Ashwin...
-----
---------------------------------------------------------
Ashwin Karpe
Apache Camel Committer & Sr Principal Consultant
FUSESource (a Progress Software Corporation subsidiary)
http://fusesource.com
Blog: http://opensourceknowledge.blogspot.com
---------------------------------------------------------
--
View this message in context:
http://camel.465427.n5.nabble.com/Instantiating-an-osgi-bundled-camel-route-from-another-bundle-tp4623697p4624769.html
Sent from the Camel - Users mailing list archive at Nabble.com.
