As a tomcat user, I am not so enthousiast about your idea of removing the sources from
the binaries.
Almost every user download only the binaries. Having the sources inside means bringing
more developers to the Tomcat project, just because it will be easier to take a look
at the sources
since tomcat 4.0 beta 5, ServletConfig is not a Wrapper anymore. To have access to the
wrapper, you need your servlet to implement the ContainerServlet (or extend, not sure
about this detail). Look at ManagerServlet for more information.
regards,
Fabien
Amy Roh [EMAIL PROTECTED] writes:
I apologize for repeating this, but I did not yet get any answer.
I wrote a servlet in a classic WAR file at an arbitrary location and NOT in the
org.apache.catalina package. From this servlet, I was able to access a method on the
Deployer, i.e. I was able to access anything public in any
Craig R. McClanahan [EMAIL PROTECTED] writes:
On 9 May 2001, Fabien Le Floc'h wrote:
Ok, this is possible to bypass the security!
Catalina conforms to the behavior in the Servlet 2.3 PFD2
Specification (Section 9.7.2) but does not comply with its
recommended behaviour.
Which
.
The only way I can make it work is to put it in the catalina.jar file. But that is
not nice at all.
Could someone help me with this?
Thank you.
Fabien Le Floc'h
P.S.: I was wondering if it was user or developer oriented... As I want to use
core Tomcat classes I thought
it work is to put it in the catalina.jar file. But that is not
nice at all.
Could someone help me with this?
Thank you.
Fabien Le Floc'h
P.S.: I was wondering if it was user or developer oriented... As I want to use core
Tomcat classes I thought it was developer but maybe I am wrong. Then I
