https://issues.apache.org/bugzilla/show_bug.cgi?id=53337
--- Comment #7 from rstoyanc...@yahoo.com ---
Thanks for the suggestions, Mark.
In the discussion on the servlet-spec user list, even wider implications were
mentioned including avoiding reliance on the requestURI or even the session
from a
https://issues.apache.org/bugzilla/show_bug.cgi?id=53337
Mark Thomas changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://issues.apache.org/bugzilla/show_bug.cgi?id=53337
--- Comment #5 from rstoyanc...@yahoo.com ---
I corrected one issue with the sample. Calling ServletB succeeds in all cases.
Calling ServletA doesn't. I updated the instructions at the project page and
updated the .war attachment.
--
You a
https://issues.apache.org/bugzilla/show_bug.cgi?id=53337
rstoyanc...@yahoo.com changed:
What|Removed |Added
Attachment #28866|0 |1
is obsolete|
https://issues.apache.org/bugzilla/show_bug.cgi?id=53337
--- Comment #3 from rstoyanc...@yahoo.com ---
Created attachment 28873
--> https://issues.apache.org/bugzilla/attachment.cgi?id=28873&action=edit
Updated .war file
--
You are receiving this mail because:
You are the assignee for the bug.
https://issues.apache.org/bugzilla/show_bug.cgi?id=53337
--- Comment #2 from rstoyanc...@yahoo.com ---
By the way, in the description above I only meant to refer to the methods
asyncContext.dispatch and request.getRequestDispatcher. I am not actually
passing "". See the link to the source code for
https://issues.apache.org/bugzilla/show_bug.cgi?id=53337
--- Comment #1 from rstoyanc...@yahoo.com ---
Created attachment 28866
--> https://issues.apache.org/bugzilla/attachment.cgi?id=28866&action=edit
.war demonstrating the issue
--
You are receiving this mail because:
You are the assignee f
