I just took a look at this and it has been fixed by Jules.
----- Original Message ----- From: "Peter Levart" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: "Jules Gosnell" <[EMAIL PROTECTED]> Sent: Saturday, December 01, 2001 7:47 AM Subject: Re: [JBoss-dev] JNDI view of java:comp context from Jetty broken > On Saturday 01 December 2001 04:20, Scott M Stark wrote: > > No, I don't see the java:comp context for this standalone war. The > > AbstractWebContainer.parseWebAppDescriptors is not being called > > as part of the deploy so the ENC is not getting created. There is some > > integration problem between Jetty and the AbstractWebContainer for > > a single war I'll look into. > > > > I dit some traceback and it appears that AbstractWebContainer subclass > (org.jboss.jetty.JettyService) is not calling > WebDescriptorParser.parseWebAppDescriptors(). > > The call to parseWebAppDescriptors() is being made from within > org.jboss.jetty.JBossWebApplicationContext.JBossSXSecurityHandler.start() > method, which is not called since no JBossSXSecurityHandler instance is ever > created. The JBossWebApplicationContext.getSecurityHandler() is never called. > > It's true. I have not yet configured the security in my app. But it should > work nevertheless. > > Why is parsing done in JBossSXSecurityHandler's start() method? Because the > start() method is called with the correct thread's contextClassLoader? If it > is different than thread's contextClassLoader when performDeploy is called > then it should be the child of it as it is asserted in the "sanity check" > being made in JBossSXSecurityHandler.start() method. > > So I made a test and moved the parseWebAppDescriptors() call from the > JBossSXSecurityHandler.start() method to the org.jboss.jetty.Jetty.deploy() > method, just before JBossWebApplicationContext.start() method is called. > > It works. > > > Peter > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
