DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=40108>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=40108


[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |




------- Additional Comments From [EMAIL PROTECTED]  2006-07-26 14:58 -------
(In reply to comment #1)
Hi Remy,

I do understand your statement. But you have to have in mind that this is not a 
must.

The requirement in Servlet 2.4 is changed from “must” to “should” on contarast 
to Servlet 2.3.

Here is the extract from the spec (SRV.S.17):

• It is now a recommendation, instead of a requirement, that the reference to 
the
request and response object should not be given to the object in other threads -
based on the requirement from JSR-168. Warnings are added when the thread
created by the application uses the objects managed by the container.(2.3.3.3)
• It is now a recommendation, that the dispatch should occur in the same thread
of the same JVM as the original request - based on the requirement from JSR-
168(8.2)

This in practice allows the request to be dispatched to servlet in a thread 
that is different than the thread of the original request. And in my scenario 
the request dispatching occurs inside the new thread and not before that.

So I think that my question has its reason. Tomcat does have a bug. There is a 
test case that can simulate it. If you need more details or examples in order 
to understand the issue, please tell and I'm ready to send it.


Regards,
Diyan






-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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

Reply via email to