Thanks Cedric, I really like the tiles solution. One of my main concerns as this application is in a hosted environment is hogging resources . I would like to avoid not having the user content existing in memory. I am going to have to test with large amounts of content and see the size of the bean object. My other main concern is speed and I would like to not have to perform file I/O for every content request. I am currently using Struts template strategy because I am performing HTTP/HTTPS switching and employing sub apps in the application that was not supported by Tiles the last time I checked, but I will migrate to this design when the functionality is supported.
Greg -----Original Message----- From: Cedric Dumoulin [mailto:cedric@;apache.org] Sent: Thursday, October 24, 2002 3:59 AM To: Struts Users Mailing List Subject: Re: Managing User defined Web Content design advice? Greg Hess wrote: > >2) Create new files for each body of content and simply <jsp:include> or ><bean:include> the page into the template. The problem here is that as the >number of links and content is user defined and I only know how to use the >include tags with static resources. Sure I could include an action but how >would I dynamically add parameters to inform the include resource as to >witch content to retrieve? I see that page param of bean:include is labeled >(RT EXPR) does this mean that I can use an expression the provide that >attribute, I have never been able to do this??? If I could do it in this >manner I think it would be cleaner but obviously not sure how. > Have you consider to use Tiles for the dynamic content ? There is a (simple) example of user customized menu and user customized portal content in the tiles-documentation.war (under examples). It should be easy to adapt the examples to serve user customized body, with dynamic attributes. One key point is that Tiles definition can be created or modified dynamically, for example in a struts action. Cedric > >Well those are my ideas, if anyone has done this before or could provide >some advise on how this should be done it would be greatly appreciated. > >Many thanks, > >Greg > > > -- To unsubscribe, e-mail: <mailto:struts-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-user-help@;jakarta.apache.org> -- To unsubscribe, e-mail: <mailto:struts-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-user-help@;jakarta.apache.org>
