DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20891>.
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=20891

Struts - Faces - Tiles FacesRequestProcessor issue + Fix

           Summary: Struts - Faces - Tiles FacesRequestProcessor issue + Fix
           Product: Struts
           Version: 1.1 Beta 3
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Struts-Faces Library
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


I am integrating Struts - Faces - Tiles in one of my applications and i ran 
into the following issue. A temporary fix is given below:
Here's an example:
I have a form and the action on the form is "/b.do"
In the struts-config.xml , "/b.do" is mapped to a tiles definition of 
"doc.mainLayout"
In the tiles-definition.xml, "doc.mainLayout" looks like
  <definition name="doc.mainLayout" path="/faces/layout/classicLayout.jsp">
          <put name="title"  value="ABC Bank Implementation using Tiles and 
JSF" />
          <put name="header" value="/faces/common/header.jsp" />
          <put name="menu"   value="/faces/common/menu.jsp" />
          <put name="footer" value="/faces/common/footer.jsp" />
          <put name="body"   value="" /> 
  </definition>
Now when i hit the submit button on the form, the FacesRequestProcessor kicks 
off, tries to find a meaningful path for doc.mainLayout and fails with the 
message that the resource is not found. 

The solution:

I extended my FacesRequestProcessor from the TilesRequestProcesor class.
That way my request would still go through the FacesRequestProcessor, but the 
tiles related action handling would be deferred to the TilesRequestProcessor.
I was able to achieve my goal after this change

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to