Ok, I probably should have noticed this quicker, but this was a bug in
Felix framework 3.0.1:
https://issues.apache.org/jira/browse/FELIX-2479
This was corrected in 3.0.2, so you have to use 3.0.2 or greater.
-> richard
On 11/5/10 12:06, ext2 wrote:
Thanks Richard:
I have post the two bundles to your private mail;
Following is the details Stack trace of the exception
java.lang.NoClassDefFoundError:
com.tongtech.ti.be.require.TestBeRequiredInterfa
ce
at
com.tongtech.ti.test.require.bundle.a.TestRequireActivator.class$(Tes
tRequireActivator.java:10)
at
com.tongtech.ti.test.require.bundle.a.TestRequireActivator.start(Test
RequireActivator.java:12)
at
org.apache.felix.framework.util.SecureAction.startActivator(SecureAct
ion.java:633)
at org.apache.felix.framework.Felix.activateBundle(Felix.java:1862)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1779)
at
org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1188)
at
org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264
)
at java.lang.Thread.run(Thread.java:619)
-----origin-----
Sender: Richard S. Hall [mailto:[email protected]]
Time: 2010/11/5 21:33
Receiver: [email protected]
Subject: Re: the required-bundles' class cannot be resolved, what's the
exact reason cause this?
I don't think you are describing the situation accurately.
You bundle can be required, i.e., the requiring bundle is wired to your
provider bundled. The issue, it appears, is that you are getting a NCDFE
under Felix framework 3.0.1 when you try to load classes from it.
You do not provide enough information to know what is going on (e.g.,
the stack trace). Looking at the change logs for version 3.0.2, we did
fix an implicit boot delegation class loading bug, but it seems unlikely
you'd be hitting that.
If the two bundles are simple, you could always email them to me privately.
-> richard
On 11/4/10 23:09, ext2 wrote:
Sorry, I forget to tell that: my usage is very simple , there is not
split-package exists, also didn't use the bundle's version to choice
required bundle, just using the bundle's symbolic-name to choice the
required bundle;
======================================================================
Hi:
Recently, I encounter a very simple usage for required-bundle. But
the class in required-bundle cannot be resolved and a
java.lang.NoClassDefFoundError raised.
When I using felix framework 3.0.1 , I find that just the bundle I
made cannot be required, but the other bundle etc: spring-beans can be
required; If I switch to felix framework 3.0.2, the bundle I made also
could be required.
I have tried to search the felix's issues , but cannot find
some-things concern of this.
Can any-one help me to point out what's the exact reason caused my
bundle cannot be required in felix framework 3.0.1?
Following is my bundles and it's header:
Bundle: be-required:
Contribute a package " com.tongtech.ti.be.require"
Bundle: be-required's Manifest:
Manifest-Version: 1.0
Bundle-Name: Unnamed - test:be.require:bundle:1.0
Build-Jdk: 1.5.0_22
Built-By: ext2xhb
Created-By: Apache Maven Bundle Plugin
Import-Package: com.tongtech.ti.be.require
Bundle-ManifestVersion: 2
Bundle-SymbolicName: test.be.require
Tool: Bnd-0.0.357
Bnd-LastModified: 1288922744796
Export-Package: com.tongtech.ti.be.require
Bundle-Version: 1.0.0
Bundle requiring's manifest:
Manifest-Version: 1.0
Built-By: ext2xhb
Created-By: Apache Maven Bundle Plugin
Bundle-Activator: com.tongtech.ti.test.require.bundle.a.TestRequireAct
ivator
Import-Package: com.tongtech.ti.test.require.bundle.a,org.osgi.framewo
rk
Bnd-LastModified: 1288922762062
Export-Package: com.tongtech.ti.test.require.bundle.a;uses:="org.osgi.
framework"
Bundle-Version: 1.0
Bundle-Name: Unnamed - test:require.bundlea:bundle:1.0
Build-Jdk: 1.5.0_22
Bundle-ManifestVersion: 2
Bundle-SymbolicName: test.require.bundlea
Tool: Bnd-0.0.357
Require-Bundle: test.be.require
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
