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=36150>. 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=36150 Summary: Redirects requred when transitioning between RDC pages using Websphere 6.0.2 Product: Taglibs Version: 1.0 Platform: All OS/Version: All Status: NEW Severity: major Priority: P1 Component: RDC Taglib AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] CC: [EMAIL PROTECTED] Here are the steps to reproduce the error, using Struts (though the issue is not struts-specific): * Voice browser submits back to JSP 1 when input matches the grammar in the RDC. The RDC now has correct input, and an rdc:struts tag forwards to Struts action 1. * Struts action 1 does whatever it needs to in response to the input, then forwards to Struts action 2 for the next page/step. * Struts action 2 forwards to the JSP for step 2. Expected behavior: The second JSP renders and the voice browser correctly interprets the second page and its RDC. (Note, if the voice browser is pointed directly to page 2, this page functions correctly). Actual behavior: The voice interpreter (one provided in IBM Voice Toolkit 6.0) complains that "Msg : The markup in the document following the root element must be well-formed." Additional details (current workaround we are using): Using redirects to transition between JSP pages fixes the symptoms. In the above example, if Struts action 1 redirects to Struts action 2 (so the voice interpreter issues a new request for the next page) the symptoms disappear and the application works properly. I believe this is due to JspWriter buffer flushing issues, where content from the partial rendering of Jsp 1 is not properly cleared before the rendering of Jsp 2. Looking over the JSP 2.0 specification, section 5.5 (page 1-111) states that when using jsp:forward, any buffered content must be flushed by the container prior to forwarding the request. I was not able to find a similar requirement for the use of RequestDispatcher.forward, which is what rdc:struts-submit uses. I don't know if this is a bug in WebSphere 6.0, and error I am making, or if this basic usage pattern in RDCs is not compatible with the specification. I've created a simple example case to demonstrate the problem, and will try to attach it to this report. It's 3.6 Megs, so if that's too big, I'll have to find some other way to submit it. -- 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]
