Thanks Cedric, I haven't gotten to develop any Tiles yet. Cedric, what is your advice on using tiles with sub-module?
danny -----Original Message----- From: Cedric Dumoulin [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 14, 2002 5:56 PM To: Struts Users Mailing List Subject: Re: Local/Global Exception Handling: How do you specify ContextRe lati ve path(action's input) in the Sub-Apps' struts-config.xml Hi, You should be able to use a tile definition name in the path of an exception. The struts exception mechanism create a forwardConfig which is treated like an normal forwardConfig. So, Tiles catch the exception forward and check for tiles definition name before struts do its forward. Cedric Craig R. McClanahan wrote: >On Tue, 13 Aug 2002, Trieu, Danny wrote: > > > >>Date: Tue, 13 Aug 2002 16:31:27 -0700 >>From: "Trieu, Danny" <[EMAIL PROTECTED]> >>Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]> >>To: 'Struts Users Mailing List' <[EMAIL PROTECTED]> >>Subject: RE: Local/Global Exception Handling: How do you specify >> ContextRe lati ve path(action's input) in the Sub-Apps' struts-config.xml >> >>Can you give me an example of how path one <exception/> can be set to a >>module-relative resource? >>This can be a JSP, Tiles' definition, or an Action relative to the module's >>config file right? >> >> >> > >The path on an exception is defined as a "module-relative URI to the >resource that will complete the request/response if an exception occurs". >In other words, Struts will tack create the complete URI by tacking the >module prefix on the front (that's what would *not* happen if a >contextRelative="true" attribute were added). > >So, if you had a JSP page at the module-relative path "/showException.jsp" >that you wanted you use, you'd just say: > > <exception ... path="/showException.jsp" ... /> > >You'll have to ask Cedric about whether Tiles treats this kind of a path >the same as the path on a <forward> so that you can reference a Tile. I >don't know the answer to that one. > > > >>Thanks, >> >>danny >> >> > >Craig > > > > >>-----Original Message----- >>From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] >>Sent: Tuesday, August 13, 2002 4:13 PM >>To: Struts Users Mailing List >>Subject: Re: Local/Global Exception Handling: How do you specify >>ContextRelati ve path(action's input) in the Sub-Apps' struts-config.xml >> >> >> >> >>On Tue, 13 Aug 2002, Trieu, Danny wrote: >> >> >> >>>Date: Tue, 13 Aug 2002 14:43:48 -0700 >>>From: "Trieu, Danny" <[EMAIL PROTECTED]> >>>Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]> >>>To: Struts Users Mailing List <[EMAIL PROTECTED]> >>>Subject: Local/Global Exception Handling: How do you specify >>> ContextRelati ve path(action's input) in the Sub-Apps' >>>struts-config.xml >>> >>>Craig, >>> >>>Do you know how this can be done? >>> >>>Thanks, >>> >>> >>> >>Currently, paths on <exception> declarations are all considered to be >>module-relative. Doing this would require the addition of a >>"contextRelative" attribute on the <exception> element, and making sure that >>the code in ExceptionHandler respected it. Filing an enhancement request in >>the bug tracking system would be appropriate: >> >> http://nagoya.apache.org/bugzilla/ >> >>if it's not there already. >> >>Personally, I have a concern about implementing this. One of the nice >>things about application modules today is that they are pretty much self >>contained and independent of each other. Starting to depend on external >>things like common exception handlers increases the fragility and complexity >>of installing a module -- no longer can you just "add a new >>struts-config.xml file and restart the webapp. You've got to make sure that >>all the shared dependencies are satisfied. >> >>Of course, the same philosophy was behind the idea that WAR files *should* >>be indepdendent and self contained, but no, everyone wants shared JAR files >>in Tomcat's common/lib directory (or the equivalent on other >>servers) ... >> >> >> >>>Danny >>> >>> >>> >>> >>Craig >> >> >> >>-- >>To unsubscribe, e-mail: >><mailto:[EMAIL PROTECTED]> >>For additional commands, e-mail: >><mailto:[EMAIL PROTECTED]> >> >>-- >>To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >>For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> >> >> >> >> > > >-- >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
