Re: Does the "isThreadSafe" page directive work in Tomcat 5.0.18?

2004-02-22 Thread QM
On Sun, Feb 22, 2004 at 12:57:26PM -0800, Josh Rehman wrote:
: I changed this directive to "false" and looked at the generated servlet. 
: I was expecting to see that it implements "SingleThreadModel" but there 
: was no change to the generated servlet code. Have I missed something? 


Tomcat5 is a servlet spec 2.4 / JSP spec 2.0 container.  Those specs
deprecate SingleThreadModel and isThreadSafe, respectively.

-QM

-- 

software  -- http://www.brandxdev.net
tech news -- http://www.RoarNetworX.com


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Does the "isThreadSafe" page directive work in Tomcat 5.0.18?

2004-02-22 Thread Josh Rehman
Damn, I've been reading the JSP 1.2 spec for some reason. Thanks.

Would it be a good idea for Tomcat to print out a warning about this 
deprecation?

QM wrote:

On Sun, Feb 22, 2004 at 12:57:26PM -0800, Josh Rehman wrote:
: I changed this directive to "false" and looked at the generated servlet. 
: I was expecting to see that it implements "SingleThreadModel" but there 
: was no change to the generated servlet code. Have I missed something? 

Tomcat5 is a servlet spec 2.4 / JSP spec 2.0 container.  Those specs
deprecate SingleThreadModel and isThreadSafe, respectively.
-QM

 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: Does the "isThreadSafe" page directive work in Tomcat 5.0.18?

2004-02-22 Thread QM
: Would it be a good idea for Tomcat to print out a warning about this 
: deprecation?

Not my say -- I'm neither on Sun's board for specs, nor a Tomcat
developer. ;)


Seriously, though: this is an issue that could argued either way, so my
guess is that the Tomcat crew decided in favor of the one way and that's
how it turned out.

-QM

-- 

software  -- http://www.brandxdev.net
tech news -- http://www.RoarNetworX.com


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]