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=36152>.
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=36152





------- Additional Comments From [EMAIL PROTECTED]  2006-04-24 22:24 -------
Thanks Don. I was checking my emails often and didn't check the bug itself - 
else I would've responsed much earlier. I was able to reproduce the problem 
with the 1.2.9 version as well. The issue is still there. 

Since I am not able to attach the entire WAR project, I am attaching the two 
classes I added to the strurs-example project to demonstrate this problem. 

1. FindCaseServlet.java
2. FindCaseServletTest.java

Add these two classes to the struts-example project and execute the 
FindCaseServletTest testcase (the URL is already in the document attached 
previously). The testcase should run for about 30 seconds, this is done 
intentionally with a dummy loop logic. When this is running - request any JSP 
form in the struts-example application. Once the page is loaded, view the HTML 
source, you should see the action path partially or completely missing. 

The trick is to keep two browser instances open, and in one instance execute 
the testcase URL and as soon as you see "FindCaseServlet.doPost.Before dummy 
loop" line in the server console - request a JSP form immediately from the 
application through the second browser instance. When the timing works right - 
you will see the HTML response with incorrect action path. 

The two class attachment follows... 



-- 
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