Mark Struberg wrote > I've tried such things once and gave up. For accessing the Remote EJB you > need some client.jar from that very server (glassfish-client.jar). And > those often contain lots of classes which really create classpath clashes. > They are really only meant for clients which do not have any EJB knowledge > at all, like say a Swing client. > [...snip...]
Yes, and Glassfish feels a little clumsy in that regard. gf-client.jar is small but its manifest has lots of relative entries pointing to the contents of Glassfish's "modules" directory. The super appclient.jar contains all the dependencies; it's basically the whole server. -- View this message in context: http://openejb.979440.n4.nabble.com/Invoke-EJB-on-Glassfish-tp4663221p4663298.html Sent from the OpenEJB User mailing list archive at Nabble.com.
