Hi Magnus! I tend to believe a CMS is way to slow to combine it with Tapestry. Furthermore if you serve pages by a CMS link you will notice a difference in Look and Feel and linking back to the T5 app may be difficult. CMS is perfect to allow a user (non dev) to edit pages like "about us", "we hire" aso without the need of a deployment (tml change) for example. And you get versioning and a wysiwyg editor for free. I would integrate parts of the CMS pages by streaming fragments, which keeps the webapp conscise and allows caching. Just my 2 cents...
Jens Sent from my iPhone On 15.06.2013, at 20:42, Bård Magnus Kvalheim <mag...@kvalheim.eu> wrote: > Maybe it's just me and I didn't see the problem, but can't you just link to > the cms content? > The cms content has a link so why should tapestry service it? > > Is it on the same base domain? Then use request services to generate an > absolute url. > > -magnus > > HTC one > Den 12. juni 2013 13:07 skrev "John" <j...@quivinco.com> følgende: > >> Hi, >> >> I have a need to link to some static HTML generated by a CMS app. Assuming >> this content is in a directory outside my Tapestry app, what would be the >> best way of linking/serving it via Tapestry? >> >> Perhaps I should just configure a seperate Jetty context and provide >> absolute URLs in someway? >> >> I'd also consider the static content being part of the projects Java >> resources, not so keen though. >> >> John --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
