and maybe tell us with which version of Felix you've been trying (0.8.0 or trunk - if trunk which revision/date)?
regards, Karl On 6/21/07, Richard S. Hall <[EMAIL PROTECTED]> wrote:
Yes. The biggest issue in switching from Oscar to Felix is that Felix generally does NOT give bundles access to anything on the class path, whereas Oscar gave them access to everything on the class path. However, if you tested this bundle on Felix with the Sun JRE and it worked, then that is odd. Could you show us your expection, manifest, and bundle content? -> richard Felix Meschberger wrote: > Hi, > > NoClassDefFoundError generally indicates a missing class to which a > class to > be loaded should be linked. For example, if you load the StringBuffer > class, > the String class is required for linking. If the String class would > not be > found, the NoClassDefFoundError is thrown - whereas a > ClassNotFoundException > would be thrown if the StringBuffer class itself was not found. > > So, in your use case, it might be, that there are missing classes > expected > from the environment (system classes, boot class path or other bundles), > which are missed. You might want to check the > org.osgi.framework.system.packages and > org.osgi.framework.bootdelegationproperties of the Felix > configuration. > > Regards > Felix > > On 6/21/07, Konstantinos N. Ntermitzoglou <[EMAIL PROTECTED]> > wrote: >> >> Hi everybody, >> >> I have recently moved from Oscar to Felix, but I am facing the >> following issue that keeps me from doing it totally. I have an API >> bundle and another one that implements it. I have been using them with >> Oscar under an arm-linux architecture with JamVM1.4.5, classpath 0.92 >> and all worked just fine. The same configuration will not work with >> Felix. When I start the implementer bundle, it seems that the wiring is >> done correctly but when the time comes for an API class to be loaded I >> am getting java.lang.NoClassDefFoundError. I have used the exact same >> configuration on an i686-linux with SUN's JVM and then the bundle was >> started successfully. >> So I believe my bundles are R4 compatible and are bundled correctly >> (Manifest import-export etc. ), so what can it be wrong ? Any ideas how >> to solve it ? >> >> Thank you in advance for any replies, >> Ntermitzoglou Konstantinos >> >
-- Karl Pauls [EMAIL PROTECTED]
