Hi Scott,
The problem with placing the protected classes in the ejb-jar is that they,
the protected classes that is, depend on other, public classes in other
packages in my application for more mundane functionality. When I try to
deploy the ejb-jar this way, it fails, as the ClassLoader that loads the
ejb-jar is not able to find the required classes needed to load the
protected objects.
I guess I could put the *entire* application in the ejb-jar, and just forget
about placing anything in lib/ext, but this seems to against the normal
concept of this jar. Is this a bad way to go? What are the problems with
this approach? I guess one nice thing is that I could truly use hot-deploy
to wipe out the application and deploy a new version without taking down the
appserver.
Thanks for your insight.
-Eric
----- Original Message -----
From: "Scott M Stark" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, September 17, 2001 7:22 PM
Subject: Re: [JBoss-user] protected classes called by an EJB
> 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
>
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
