-
1. Re: .NoClassDefFoundError: javax/ejb/SessionBean
tdang Sep 16, 2002 5:53 AM (in response to mohamed)Be sure that you've added jar files of JBoss into your classpath.
Regards. -
2. Re: .NoClassDefFoundError: javax/ejb/SessionBean
mohamed Sep 16, 2002 6:52 AM (in response to mohamed)Hi tdang,
Thanks for your response, If classpath is the problem then how come I get the exceptions for only few beans, the other deplpoy fine.
Zafer -
3. Re: .NoClassDefFoundError: javax/ejb/SessionBean
ctibor Sep 27, 2002 12:22 PM (in response to mohamed)I have the exact same issue. Some EJBs deploy without a problem while others fail during deployment with the error "NoClassDefFoundError:javax/ejb/..." . I am able to repeat this error in version 2.4.6 and version 3.0.0. Furthermore, I was able to take the "undeployable" EJBs and deploy them successfully to Sun's J2EE reference implementation server. Therefore, I am suspicious that this is an issue with JBoss rather than my beans.
There is a work-around, but I am not sure why it works. If you start JBoss with the javax/ejb/* classes in the system classpath, there are no more NoClassDefFoundErrors and all of my beans deploy without any problems. Is there a classloader bug or issue within JBoss that is causing this behavior? Any insight would be greatly appreciated.
Thanks,
Chad -
4. Re: .NoClassDefFoundError: javax/ejb/SessionBean
ctibor Sep 27, 2002 12:33 PM (in response to mohamed)I have the exact same issue. Some EJBs deploy without a problem while others fail during deployment with the error "NoClassDefFoundError:javax/ejb/..." . I am able to repeat this error in version 2.4.6 and version 3.0.0. Furthermore, I was able to take the "undeployable" EJBs and deploy them successfully to Sun's J2EE reference implementation server. Therefore, I am suspicious that this is an issue with JBoss rather than my beans.
There is a work-around, but I am not sure why it works. If you start JBoss with the javax/ejb/* classes in the system classpath, there are no more NoClassDefFoundErrors and all of my beans deploy without any problems. Is there a classloader bug or issue within JBoss that is causing this behavior? Any insight would be greatly appreciated.
Thanks,
Chad