>[EMAIL PROTECTED] wrote:
>
>> I am trying to run T4m4 with my webapp and I am receiving a
>>
>> java.lang.SecurityException : sealing exception
>>
>> This is because my servlet is trying to instantiate a singleton object
>> in the webapp that reads its config info from a file on the classpath
>>
I am trying to run T4m4 with my webapp and I am receiving a
java.lang.SecurityException : sealing exception
This is because my servlet is trying to instantiate a singleton object in
the webapp that reads its config info from a file on the classpath using a
mildy modified version of the XML ma
> I suggest we consider not including the AccesLogValve in the default
> configuration until some optimization work is done on it.
>
I would suggest that you don't remove it from the default, as TC4 is not
even beta, and the nice access log is one of the reasons I am using it.
Scott Sanders
>> > - I start a new revolution in tomcat3.2 space ( proposals/something
>> > ), and all the implementation of 2.3 and all controversial stuff
>> > will go there ( i.e. all new features, like dav, http1.1, resource
>> > caching, the new SMTP and POP3 protocols - since any feature will be
>> > in f
>> I believe development on the 3.x tree MUST continue, until Tomcat 3.x
>> truly IS the RI of Servlet 2.2. Anything else would not make sense.
>> The numbering (3.2, 3.3) does not matter.
>>
>
> You will find that the 3.3 tree is pretty nearly as big an
> architectural change (from 3.2) as is 4
Everyone,
I see no reason why Tomcat 3.x and 4.x have to be mutually exclusive. As
far as I can tell, Tomcat 3.x is Servlet 2.2, and Tomcat 4.x is Servlet
2.3. It's as simple as that. Yes, the vote did happen. You now have
Tomcat 4.x, and that is what I am using, and it is awesome! Craig
