Modify the popup window ActionForward handling to forward to a framework JSP
(or Servlet) instead of writing directly to the response in the
DefaultActionForwardHandler
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: BEEHIVE-1073
URL: http://issues.apache.org/jira/browse/BEEHIVE-1073
Project: Beehive
Type: Improvement
Components: NetUI
Versions: V1, 1.0.1, v.next
Reporter: Carlin Rogers
Assigned to: Carlin Rogers
Fix For: v.next
I have a request to change the design of the popup window ActionForward
handling to forward to a framework JSP (or Servlet) instead of writing directly
to the response in the DefaultActionForwardHandler. Currently, when the
DefaultActionForwardHandler.processForward() routine gets the "_auto" Forward
of the return to page flow, we write directly to the response (just with our
own javascript, no other markup) and return null. This is a perfectly legal and
valid design. However, a design change is needed to support framework
implementations (portal) that have a sort of two phase process of first running
the action, then including the rendering of return URI from the ActionForward.
The change would be that the DefaultActionForwardHandler.processForward() would
no longer write any markup to the response. Instead it would return an
ActionForward with a path to a JSP or servlet that would handle the actual
rendering.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
