Matteo

I’d love to pretend I know the exact answer to your question, but here are a few things I do know.

1. I have used a modified jsp paragraph renderer and it seems to work, but its really kludgy. It wants to “start the request over” each time a requestDispatcher.include happens. Railo right now also wants to encode the output and put it on the OutputStream instead of using the Writer, which is another big problem because it munges everything.

2. Railo (and the language CFML) are incredibly powerful rapid application framework and language, and so not primarily for “dumb” templating. As such they do things like process events like onSessionStart and onApplicationStart, and generally have a whole range of enterprise class features (pdf creation, form building, trivially easy querying/grouped output, OO language constructs, mail, image manipulation). Exiting the template, back to the container for an include, context switching like this doesn’t do anything for railo->railo, it only hurts performance. What we really want is to set the paragraph’s context, and then call to the templatePath of the paragraph.

3. The reimplementation of is pretty clean, although it does rely on some of your underlying API. I would be sad to see some of those objects be hidden behind DI where I couldn’t get a reference to them. Check it out here: https://www.joshuafrankamp.com/svn/incubator/magnolia-railo-sample/trunk/tags/cms/includeTemplate.cfm It uses ParagraphManager’s singleton nature to get a reference and perform the template lookups (although it wouldn’t be that hard to look it up manually). I could always switch on the paragraphs type, and call the real if it were anything else besides cfm.

Perhaps some of the Railo guys can come along and tell us how to call from an API perspective, because that would take care of our custom paragraph renderer.

Joshua

Cool stuff! It’s always great to see people digging into Magnolia and coming up with stuff we didn’t think of !

Did you consider implementing a custom ParagraphRenderer for this? I don’t know the Railo API, I’m a little surprised it doesn’t have entry points outside the servlet. Well, assuming it does, maybe you’re going to tell me you would lose the JSP taglib support if you went that way ? We’re actually currently working towards extracting (at least some of) the business off of our JSP tags, in order to facilitate integration with other rendering technologies. I might blog about that in the coming weeks, so keep your eyes peeled; I’ll need feedback from people like you, to see if we’re on the right track!

Cheers,

-greg