From: <nik...@va...> - 2001-03-21 19:06:25
|
Hi Robert! I divided this thread in two. :) >> 2. [Might be off-topic] >> When running two servlets -- compiled from Jython-sources -- in two >> different contexts under Tomcat, I run into problems. Tomcat cannot find the >> second servlet, unless I put its classes (regular + inner) in the same >> context (i.e. in the same (WEB-INF/classes). At first, I thought it was due >> to the "inner class"; but it seems that I have to move both in order for the >> servlet to be found. This does not seem to happen to regular Java-servlets >> though, which is why I wonder if it's a Jython-problem. >> My question here is really if someone else has had any problems like >> this and has a suggestion at hand; otherwise, I will do some more tracking >> of the problem to see what I might have overlooked. > >I've only had success with the inner-class and class-proper in the same >context. The good stuff in Servlet2.2 containers is the ease of making >self-contained webapps, so I'm a bit confused about what the advantages of >defeating this feature would be. (or I misunderstood :) > I've probably described things rather poorly. :) I do want to have inner and proper in the same place. But two servlets (i.e. 2 * 2 files), each running in it's own context, didn't seem to work. As if the first, when initialized by the engine (Tomcat), somehow locks stuff that make Jython unable to find the other servlet. It's a bizarre problem (if I for instance remove the first servlet from Tomcat initialization, the other is suddenly found). I'm too tired to dare try and explain further I'm afraid :); I'll try to produce a better analysis and description later (I don't even have access to the machine right here.) Hopefully; I haven't missed something obvious (since it's such a strange problem). |