Why not place the EJBs + the package access classes in the ejb-jar and the
rest in
a jar in lib/ext?
----- Original Message -----
From: Eric Lindauer
To: [EMAIL PROTECTED]
Sent: Monday, September 17, 2001 3:57 PM
Subject: [JBoss-user] protected classes called by an EJB
Hi,
I'd like to deploy an EJB that calls methods in a protected class in its own
package. I am currently trying to do this by jarring up all the protected
classes, along with the rest of my application, into a .jar file which I
place in lib/ext. In the ejbs deploy jar, I only place the minimum classes
( Home, Remote, Bean, etc. ).
I suspect that the problem arises because the EJB and the jar are loaded by
different ClassLoaders, leading to SecurityExceptions. It won't work to
place the protected classes in the EJB jar, as they are dependent on other,
public classes in different packages, etc... I could conceivably end up
placing my whole application in there. And to automate figuring out which
classes need to be present, fuhgedaboudit.
So... any ideas? It doesn't kill my application to just make the other
classes public, but things would be a lot cleaner if they weren't. Thanks
for any help.
Yours,
Eric
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
