>>> 2. Finite control of what IS and ISN'T loaded > - maybe you have classes under WEB-INF/classes that are not servlets, > if so tomcat needs to distinguish between the 2 and only give > access to those that are servlets, and it because a big mess. << > > Beans are classes under that structure, but are not servlets. They need > to be accessible, surely? > > I'm writing as someone who has encountered exactly the problem you > describe with Tomcat 4.1.18. I solved it with servlet mapping, but I > cannot get my beans to work.
Yes they need to be accessible, but what I am speaking of is exposing the class DIRECTLY to a HTTP request is what they are trying to avoid. Now for your instance of not being able to access your BEANS, I would have to see what is going wrong to understand. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
