You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Carlin Rogers (JIRA)" <de...@beehive.apache.org> on 2006/02/28 23:00:40 UTC
[jira] Created: (BEEHIVE-1073) Modify the popup window
ActionForward handling to forward to a framework JSP (or Servlet) instead
of writing directly to the response in the DefaultActionForwardHandler
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
[jira] Updated: (BEEHIVE-1073) Modify the popup window
ActionForward handling to forward to a framework JSP (or Servlet) instead
of writing directly to the response in the DefaultActionForwardHandler
Posted by "Carlin Rogers (JIRA)" <de...@beehive.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-1073?page=all ]
Carlin Rogers updated BEEHIVE-1073:
-----------------------------------
Attachment: j1073-patch.txt
Attaching a patch that can be used to resolve this feature change request.
This design change started with some off line discussion, however, before committing this I'd like to post some of the details to the dev list. I also include a couple of questions for the dev list. Any feedback is appreciated and I'll rework this patch as needed and then commit it. Thanks.
> 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
> Assignee: Carlin Rogers
> Fix For: v.next
> Attachments: j1073-patch.txt
>
> 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
[jira] Resolved: (BEEHIVE-1073) Modify the popup window
ActionForward handling to forward to a framework JSP (or Servlet) instead
of writing directly to the response in the DefaultActionForwardHandler
Posted by "Carlin Rogers (JIRA)" <de...@beehive.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-1073?page=all ]
Carlin Rogers resolved BEEHIVE-1073:
------------------------------------
Resolution: Fixed
Assign To: Alejandro Ramirez (was: Carlin Rogers)
This is fixed with revision 389801,
http://svn.apache.org/viewcvs?rev=389801&view=rev
The revision updates beehive-netui-config.xml and web.xml files in the test apps and samples to configure the XHR servlet to handle the ActionForward and render the desired javascript in the response.
The popup window tests pass.
> 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
> Assignee: Alejandro Ramirez
> Fix For: v.next
> Attachments: j1073-patch.txt
>
> 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