It has been partly fixed ! You'll be all right as long as you do not expect the ENC stuff to be set up at initialise (Servlet.init()) time...
A change occured between Jetty-3.1.3 and 3.1.4, in the order in which security and other handlers/interceptors are applied, which meant that ENC stuff was not being setup before the security code looked for it. I then worked around this by doing it in the security handler/interceptor, thinking that this was added to every webapp, not just a decorator on those requiring security. This is why it worked for some people and not for others. I've moved it back into non-security code for the time being, whilst I look for a decent solution. This is my priority at the moment, so please bear with me. Jules --- Scott M Stark <[EMAIL PROTECTED]> wrote: > > 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 ________________________________________________________________ Nokia 5510 looks weird sounds great. Go to http://uk.promotions.yahoo.com/nokia/ discover and win it! The competition ends 16 th of December 2001. _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
