>>As with Struts, the JSP pages for a JSF app can certainly be in >>subdirectories ... just include the subdirectory names in your navigation >>rules for the <from-view-id> and/or <to-view-id> elements.
Is there any way to use values in the session to configure which subdirectory to go to instead of hard coding the sub directory in the xml file? so if I am using the struts-app07.xml I can just put /intro.jsp in a to-view-id or from-view id and it will know to go to the app07/app/IA/FormApp07/intro.jsp. In struts we had a helper method that checked if it ended with a .jsp and added the path to the action forward but in Shale/JSF it just returns a string so there is no altering the path to a subdirectory. Seems to me I would have to override one of the classes that controls navigation to do this. Shawn -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Craig McClanahan Sent: Tuesday, December 20, 2005 1:22 PM To: Struts Users Mailing List Subject: Re: [struts->shale jsf] On 12/20/05, Garner, Shawn <[EMAIL PROTECTED]> wrote: > > In struts we have an struts config struts-app06.xml and a > struts-app07.xml > file as well as a struts-config.xml > > It would have non year specific stuff in the struts-config.xml base > directory but then the would redirect to the app06 or app07 modules for > year > specific stuff and the JSP pages would be in a directory like > app/state/appnameyear. > > Is this type of configuration possible in JSF/Shale? Yes, it is possible to have more than one faces-config.xml file in the same way you can have more than one struts-config.xml file. Specify a comma-delimited list of context-relative paths (such as /WEB-INF/faces- app06.xml) for the context init parameter "javax.faces.CONFIG_FILES". As with Struts, the JSP pages for a JSF app can certainly be in subdirectories ... just include the subdirectory names in your navigation rules for the <from-view-id> and/or <to-view-id> elements. Shawn Craig **************************************************************************** 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. **************************************************************************** --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
