Cedric - I've been using Struts/Tiles to implement a tabbed display page, and in general it works very nicely.
However, I think there is an oversight in the tabsLayout example, which will cause a problem in use. This has to do with how the href is calculated for the links in the tabs. In the iteration through the tabsList, this code is setting the href for each tab: // compute href String href = request.getRequestURI() + "?"+parameterName + "=" + index; By doing this, we will end up with a link to the jsp file of the tabbed display page, which we don't want, rather than a link to the action that calls the jsp, which is what we do want. By doing it the way it is done in the tabsLayout.jsp, the links from the tabs will not go through an action and will not go through the Struts controller, and therefore won't be able to process the Tiles. For example, what we want to see in a tab href is: http://localhost:8080/wctemplates/tabstemplate.do?tab=1 However, what we do see is: http://localhost:8080/wctemplates/tabsLayout.jsp?tab=1 What needs to happen, is for each tab href to be a link that is made up of the action name, i.e."/servlet/tabAction.do?selected=1". Have you experienced this issue, or had any previous inquiries about this? What are your thoughts? Thanks, Don Peterkofsky -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
