Eclipse Community Forums: Virgo » Import-Package weird

Home » Eclipse Projects » Virgo » Import-Package weird

Wed, 04 April 2012 10:27

Eclipse User

This is as simple as it can get, I think.

I deploy a bundle (drop it in pick-up) and it throws:

Import-Package could not be resolved. Caused by missing constraint in bundle <com.eugene.osgi-common_1.0.0.SNAPSHOT>
constraint: <Import-Package: com.google.common.base; version="0.0.0">

Then I do
osgi> clload com.google.common.base.Ascii

Successfully loaded [com.google.common.base.Ascii] from:
134 com.eugene.core.osgi-common-core

If virgo says it's there, why can't it load it?

I am using maven bundle plugin to create the bundles.

Thx,
Eugene.

Re: Import-Package weird [message #836499 is a reply to message #836476]

Wed, 04 April 2012 11:02

Eclipse User

Just because com.eugene.core.osgi-common-core can load the class doesn't mean to say that com.eugene.core.osgi-common-core exports the package. Wink

Re: Import-Package weird [message #837140 is a reply to message #836499]

Thu, 05 April 2012 06:08

Eclipse User

True

my bad actually.

The thing is that I am trying to use some class that actually uses jndi. I have a bundle that exports : "org.apache.qpid.jndi.PropertiesFileInitialContextFactory", I can see that it really is exported with clexport.

And I have another bundle that is trying to use that class, but it fails with ClassNotFoundException. It probably has to do with class loading issue..

Re: Import-Package weird [message #839798 is a reply to message #837140]

Mon, 09 April 2012 03:57

Eclipse User

Hi,

Can you please describe in more details the scenario and also how you are trying to use JNDI.
Also can you tell us whether you are using some OSGi JNDI implementation (e.g. Gemini Naming)

Thanks
Violeta

Previous Topic:	Fresh installation problem
Next Topic:	OSGI reference Bean not found

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Jun 15 15:09:00 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter