Hi John I use (basically) OutputRaw for something similar. You can either try to use a regex to strip all unwanted elements from the CMS html or mark a div or introduce a new element (easier to exactly find the content and drop the rest). Unfortunately most work is related to "links": you have to make CMS links compatible to the Tapestry way.
So write a component which accepts the url/name/id of your CMS content as parameter and when rendering load the page, strip unwanted content and uses OutputRaw to stream the CMS data in your page. Furthermore I propose you cache the stripped content (use guava cache for example) to avoid accesing a slow CMS on each request. Jens Sent from my iPhone On 12.06.2013, at 12:08, "John" <j...@quivinco.com> wrote: > 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
