| [m7] import package problem [message #38435] |
Wed, 24 March 2004 11:19  |
Eclipse User |
|
|
|
Originally posted by: alexsmr.sympatico.ca
Hi,
In my project I created a plugin that provide some package to OSGi, I have
also created pure OSGi type bundle that imports the package from that plugin
(I have require header for my plugin ). But with or without import-package
clause I am getting exception. Something like this with import clause:
org.osgi.framework.BundleException: The bundle could not be resolved.
Reason: missing imported package com.trillint.facelet.component
and CLassNotFound exception without import clause.
Any ideas?
Thanks,
Alex.
|
|
|
|
|
|
|
| Re: [m7] import package problem [message #39266 is a reply to message #39174] |
Wed, 31 March 2004 19:21  |
| Eclipse User |
|
|
|
Originally posted by: pascal.ibm.canada
In the R3.0 of the spec, nothing is said about when the bundles should
be set to the RESOLVED state. It is up to the implementation to do it
lazily or eagerly.
Here is an excerpt of spec:
6 - The bundle’s state is set to INSTALLED.
7 - If the bundle has not declared an Import-Package Manifest header
(that is, the bundle does not depend on any packages from other OSGi
bundles), the bundle’s state may be set to RESOLVED.
PaScaL
Alex Smirnoff wrote:
> Pascal,
>
> When installing the bundle it tries to resolve dependencies and enter
> RESOLVED state. As far as I understand "Require-Bundle" and
> "Provide-Package" are eclipse additions to OSGi standard that
> come with a cost of "refreshing" packages after installation part.
> In other words, it will not resolve dependencies during installation
> phase (unless you explicitly refresh packages).
>
> So that part doesn't seems to me very compliant with OSGi.
>
> Thanks,
> Alex.
>
>
>>Just realized that my previous post was not really helpful...
>>Why are you saying that it "doesn't seems to be standard OSGi procedure"?
>>Also could you provide a simplified version of this example, I'm not
>>sure I'm getting what you are saying.
>>
>>PaScaL
>>
>>Alex Smirnoff wrote:
>>
>>
>>>Sorry to bother. I didn't refresh packages after bundle installation.
>
> Now it
>
>>>works. Doesn't seems to be standard OSGi procedure though.
>>>
>>>Alex.
>>>
>>>
>>>
>>>>In my project I created a plugin that provide some package to OSGi, I
>
> have
>
>>>>also created pure OSGi type bundle that imports the package from that
>>>
>>>plugin
>>>
>>>
>>>>(I have require header for my plugin ). But with or without
>>>
>>>import-package
>>>
>>>
>>>>clause I am getting exception. Something like this with import clause:
>>>>
>>>>org.osgi.framework.BundleException: The bundle could not be resolved.
>>>>Reason: missing imported package com.trillint.facelet.component
>>>>
>>>>and CLassNotFound exception without import clause.
>>>>
>>>>Any ideas?
>>>>
>>>>Thanks,
>>>>Alex.
>>>>
>>>>
>>>
>>>
>>>
>
>
|
|
|
| Re: [m7] import package problem [message #39297 is a reply to message #39266] |
Thu, 01 April 2004 08:51 |
| Eclipse User |
|
|
|
Originally posted by: alexsmr.sympatico.ca
Sorry. Hmm... Somehow I missed that point and was pretty sure that
after installation and if dependencies are resolved bundles must enter
RESOLVED state. Looks that I was wrong.
Thanks for pointing me to the right direction,
Alex.
"Pascal Rapicault" wrote:
> In the R3.0 of the spec, nothing is said about when the bundles should
> be set to the RESOLVED state. It is up to the implementation to do it
> lazily or eagerly.
> Here is an excerpt of spec:
>
> 6 - The bundle
|
|
|
Powered by
FUDForum. Page generated in 0.04281 seconds
Home