That is not what njar is being used for, and it is not working with security policies. The full name under deploy is being used to establish security policies. Another solution I'm looking at involing the custom class loader policy handling suggested by Adrian requires neither a custom protocol or the full pathname under deploy.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Hiram Chirino" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, March 11, 2002 6:22 AM Subject: RE: [JBoss-dev] Jasper problems - Eureka ! > > The reason njar was introduced in the first place was so that we could apply > a security policy to the classes that are in a nested jar. Scott seems to > have had some success doing that with njar and the sun jdk. > > Regards, > Hiram > > >From: "marc fleury" <[EMAIL PROTECTED]> > >To: "Hiram Chirino" <[EMAIL PROTECTED]>, > ><[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> > >CC: <[EMAIL PROTECTED]> > >Subject: RE: [JBoss-dev] Jasper problems - Eureka ! > >Date: Mon, 11 Mar 2002 04:57:16 -0800 > > > >i haven't really delved into the njar stuff but at this point it seems we > >are complicating the problem with it. > > > >can't we just unjar all the jars that arrive with web stuff and be done > >with > >problem? > > > >yes it will break the jsp if you don't have a filesystem but let's face it > >running a webserver without a filesystem is not ideal, > > > >marcf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
