Scott, AFAIK (and in this area it's not much):
ENC=Enterprise Naming Context. This is implemented via JNDI. Jetty does not contain any JNDI related code - since this stuff only becomes relevant within e.g. JBoss. Thus it is all left to the integration code. The integration code does not contain any JNDI stuff. This is all left to my superclass - AbstractWebContainer. JBoss-2.4.0/Jetty-3.1.RC8 works. JBoss-2.4.1/Jetty-3.1.RC9 and JBoss-2.4.1/Jetty-3.1.1 display the problem. I have built JBoss-2.4.0/Jetty-3.1.RC9 and 3.1.1 distributions which both DO NOT display the problem. I have built a 2.4.2 release which does.display the problem. On the subject of the ClassLoader used for the webapp by Jetty. I have run some tests and this is ALWAYS the actual ClassLoader passed to it by the or a descendent of this. So as far as I understand (unless I am mistaken about what the ENC is): 1. Jetty does not and has never created the war ENC, but expects AbstractWebContainer to do so. 2. Some change seems to have occurred between 2.4.0 and 2.4.1 which has possibly exacerbated a shortfall in the Jetty integration. 3. The stacktrace shows that AbstratWebContainer is trying to bind a resource that has already been bound - possibly by it. I would really like to put this to bed sso and get a 2.4.2 release out. Any help that you can give me on this would be much appreciated, Why particularly do you implicate ClassLoaders? Would class name spaces have any relevance to JNDI namespaces ? could you explain. Jules Scott M Stark wrote: > I tried deploying the website.ear to JBoss-2.4.1a/Tomcat-3.2.3 and this > works. There must be an issue with Jetty not creating the war ENC with > the war class loader established as the thread context class loader. Show > the full stack trace of the exception. > > ----- Original Message ----- > From: "Jason Dillon" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday, September 27, 2001 6:20 PM > Subject: [JBoss-dev] problem with 2.4.1/jetty & jboss-website > > > I am getting this exception when deploying jboss-website to a freshcopy of > > jboss-2.4.1 with jetty/3.1.1: > > > > <snip> > > javax.naming.NameAlreadyBoundException; remaining name 'env' > > at > > org.jnp.server.NamingServer.createSubcontext(NamingServer.java:451) > > at > > org.jnp.interfaces.NamingContext.createSubcontext(NamingContext.java:648) > > at > > org.jnp.interfaces.NamingContext.createSubcontext(NamingContext.java:634) > > at > > > org.jboss.web.AbstractWebContainer.parseWebAppDescriptors(AbstractWebContain > er.java:292) > > at > > > org.jboss.web.AbstractWebContainer$DescriptorParser.parseWebAppDescriptors(A > bstractWebContainer.java:406) > > at org.jboss.jetty.SetupHandler.start(SetupHandler.java:63) > > at org.mortbay.http.HandlerContext.start(HandlerContext.java:1152) > > at > > > org.mortbay.jetty.servlet.WebApplicationContext.start(WebApplicationContext. > java:338) > > </snip> > > > > It looks like the manual.ear deploys fine (which just has manual.war > > inside), but webside.ear failes (which has jbossgroup.war, website.war & > > snapshots.war). > > > > I am going to try and muck with the config somemore, but if anyone has any > > clues... > > > > --jason > > > > > > _______________________________________________ > > Jboss-development mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
