Re: DO NOT REPLY [Bug 10842] New: - Including an Action does not work if response had already been committed

2002-07-15 Thread James Holmes

This sounds like an enhancement to me.

Anybody else??

-james
[EMAIL PROTECTED]
http://www.jamesholmes.com/struts/


--- [EMAIL PROTECTED] wrote:
> DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
> 
> RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE
> AT
>
.
> ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED
> AND 
> INSERTED IN THE BUG DATABASE.
> 
>
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10842
> 
> Including an Action does not work if response had
> already been committed
> 
>Summary: Including an Action does not
> work if response had
> already been committed
>Product: Struts
>Version: 1.1 Beta 1
>   Platform: All
> OS/Version: All
> Status: NEW
>   Severity: Normal
>   Priority: Other
>  Component: Controller
> AssignedTo: [EMAIL PROTECTED]
> ReportedBy: [EMAIL PROTECTED]
> CC: [EMAIL PROTECTED]
> 
> 
> Struts has a nice way to map named paths via
> ActionMappings defined in the 
> struts-config.xml file. Some of us may decide to
> implement view logic as an 
> Action over a Servlet to leverage the ActionMapping
> capabilities. Thus some of 
> these actions may not have an ActionForm associated
> to them. In a template-like 
> implementation some jsp pages may need to *include*
> an Action that decides 
> which template body to include. The problem is
> *including* an Action will 
> result in invokation of the ActionServlet which
> performs a *forward* to the 
> ActionForward path. Problems occur if the content of
> jsp page containing the 
> jsp:incude call had begun to be committed to the
> client. See SRV.8.4 in the 
> Servlet2.3 spec.
> 
> The ActionServlet needs to be smart enough to
> perform an *include* to its 
> ActionForward path if the ActionServlet itself had
> been included. One way the 
> ActionServlet can determine if it has been included
> is to check for the request 
> attribute "javax.servlet.include.request_uri". If
> its null then it is free to 
> *forward* to the ActionForward path. If its not
> null, then it should *include* 
> the ActionForward path.
> 
> --
> To unsubscribe, e-mail:  
> 
> For additional commands, e-mail:
> 
> 


__
Do You Yahoo!?
Yahoo! Autos - Get free new car price quotes
http://autos.yahoo.com

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 




DO NOT REPLY [Bug 10842] New: - Including an Action does not work if response had already been committed

2002-07-15 Thread bugzilla

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10842

Including an Action does not work if response had already been committed

   Summary: Including an Action does not work if response had
already been committed
   Product: Struts
   Version: 1.1 Beta 1
  Platform: All
OS/Version: All
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Controller
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]


Struts has a nice way to map named paths via ActionMappings defined in the 
struts-config.xml file. Some of us may decide to implement view logic as an 
Action over a Servlet to leverage the ActionMapping capabilities. Thus some of 
these actions may not have an ActionForm associated to them. In a template-like 
implementation some jsp pages may need to *include* an Action that decides 
which template body to include. The problem is *including* an Action will 
result in invokation of the ActionServlet which performs a *forward* to the 
ActionForward path. Problems occur if the content of jsp page containing the 
jsp:incude call had begun to be committed to the client. See SRV.8.4 in the 
Servlet2.3 spec.

The ActionServlet needs to be smart enough to perform an *include* to its 
ActionForward path if the ActionServlet itself had been included. One way the 
ActionServlet can determine if it has been included is to check for the request 
attribute "javax.servlet.include.request_uri". If its null then it is free to 
*forward* to the ActionForward path. If its not null, then it should *include* 
the ActionForward path.

--
To unsubscribe, e-mail:   
For additional commands, e-mail: