Thanks for your response... your suggestion worked! However, it would be nice to be able to use a path in the tiles name as well. This would help keep the tile names organized and remove any concern of tile name duplication. Also, keeping the tile name and JSP name consistent allows visual tools (I am using Exadel) to better assist with configuration updates.
Do you know why I am unable to add a path to the tile name? To me this seems like a bug... do you agree? Thanks for your help! Kirk -----Original Message----- From: Johannes Hiemer [mailto:[EMAIL PROTECTED] Sent: Friday, August 19, 2005 7:39 AM To: MyFaces Discussion Subject: Re: MyFaces tiles problem Hi, normally it should be enough to define in your tiles.config: <definition name="page2.tiles" extends="layout.example" > <put name="body" value="/pages/page2.jsp" /> </definition> and in your navigation: <navigation-rule> <from-view-id>/pages/page2.jsp</from-view-id> <navigation-case> <from-outcome>back</from-outcome> <to-view-id>/page1.jsp</to-view-id> </navigation-case> </navigation-rule> Did you try that? Regards Johannes "MyFaces Discussion" <[email protected]> schrieb am 19.08.05 04:49:05: > > > I deployed the "myfaces-tiles-example.war" example application that is included in the MyFaces distribution. While experimenting with this application, I attempted to reorganize the location of some of the JSP files. Basically I wanted to be able to separate the pages into several folders according to functionality. I moved one sample page into a sub-folder, and I performed the following changes to the example application... > > > > 1) created a "pages" folder within the root web context > > 2) Moved the "pages2.jsp" file to the "pages" folder > > 3) Modified the "pages2" navigation rule in the "tiles-faces-config.xml". > > <navigation-rule> > > <from-view-id>/pages/page2.jsp</from-view-id> > > <navigation-case> > > <from-outcome>back</from-outcome> > > <to-view-id>/page1.jsp</to-view-id> > > </navigation-case> > > </navigation-rule> > > 4) Modified the "pages2" tiles definition in the "tiles.xml" file. > > <definition name="/pages/page2.tiles" extends="layout.example" > > > <put name="body" value="/pages/page2.jsp" /> > > </definition> > > 5) I left the "navigation.jsp" file unchanged. > > <h:commandLink action="nav_page2"> > > <h:outputText value="Page2" /> > > </h:commandLink> > > > > The first time I navigated to "nav_page2" from the the "navigation.jsp" page, the page seemed to display fine. However, the next time I tried to navigate to the page (by clicking on the "Page2" link in the navigation page) the page displayed with a really strange format. The raw content of the page was displayed, but the CSS and div tags seemed to have been ignored. > > > > Has anyone successfully used the tiles integration with pages that are not in the root content? Can anyone see something I am doing wrong? > > > > Thanks much, > > Kirk Larson > > > > **************************************************************************** > > This email may contain confidential > material. If you were not an intended recipient, > Please notify the sender and delete all copies. > We may monitor email to and from our network. > > *************************************************************************** ______________________________________________________________________ XXL-Speicher, PC-Virenschutz, Spartarife & mehr: Nur im WEB.DE Club! Jetzt gratis testen! http://freemail.web.de/home/landingpad/?mc=021130 **************************************************************************** This email may contain confidential material. If you were not an intended recipient, Please notify the sender and delete all copies. We may monitor email to and from our network. ****************************************************************************
