I'm using NetBeans RCP to build a standalone J2EE application, that talks with
remote EJBs deployed into a glassfish server.
I'm getting the exception below (ClassNotFound,
com.sun.ejb.containers.GenericEJBHome).
I think the problem is related to the way NetBeans uses classloaders internally.
I wonder if it would be possible for you to use a
"Thread.currentThread().getContextClassLoader()" when dinamically creating
remote ejb stubs/skeletons so that remote EJB classes can be loaded correctly.
I've submitted an issue to the NetBeans team on this:
I think that it's important to be able to access remote EJBs from within
NetBeans RCP applications, as NetBeans RCP is the best architecture out there to
build complex Swing applications.
Hi,
I'm using NetBeans RCP to build a standalone J2EE application, that talks with remote EJBs deployed into a glassfish server.
I'm getting the exception below (ClassNotFound, com.sun.ejb.containers.GenericEJBHome).
I think the problem is related to the way NetBeans uses classloaders internally.
I wonder if it would be possible for you to use a "Thread.currentThread().getContextClassLoader()" when dinamically creating remote ejb stubs/skeletons so that remote EJB classes can be loaded correctly.
I've submitted an issue to the NetBeans team on this:
http://www.netbeans.org/issues/show_bug.cgi?id=151368
(there's a test case there)
I think that it's important to be able to access remote EJBs from within NetBeans RCP applications, as NetBeans RCP is the best architecture out there to build complex Swing applications.
Environment
Operating System: All Platform: All
Affected Versions
[current]