Rickard �berg wrote:
> Hm.. wwwait a minute.. I know what it is :-( We copy jars on deploy so
> that we can undeploy and redeploy without getting file access problems.
> The copy in the tmp dir is not in the same place as the original jars,
> so the references break.
>
> Damn. Knew this would come some day. So, if we don't copy the references
> work, and if we copy the references break.
>
> Either:
> 1) Don't copy and try to do read-only ClassLoading from it
> 2) Copy, but check the jar and add the Class-Path manifest header
> references to the EJB classloader
>
> 2) is fairly simple and would work. However, if we could get around the
> need to copy to tmp that would be better.
>
> Comments?
Alright, you had your chance. Too late. I have now implemented 2). It is
in CVS. :-)
Basically, on deploy the jar is checked for Class-Path manifest header.
If present all the entries are added to the classloader, and relative
from the place the original jar was and not the copied tmp file.
BTW, as I updated ContainerFactory.deploy I noticed that EJBClassLoader
is not used. Why not!? Who removed this ('cause I know that I used it
back when I first coded deploy()). Removing it will make it impossible
to enforce EJB security restrictions.
/Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
