On Mon, Sep 27, 2010 at 3:59 AM, <[email protected]> wrote: > I'm happy to hear that XTC has actually been used in production. That's > enough for me to try to use it myself. > > I suppose the whole integration shouldn't be so difficult altogether. All > that there really is to do, is to override AbstractUrlBasedView which amounts > to implementing a single method: > > void renderMergedOutputModel(Map<String, Object> model, HttpServletRequest > request, HttpServletResponse response) throws Exception; > > after which the whole layout should be outputed to the response stream > object. Inside the method, the path to rendered page template is available. > The model parameter associates names of variables with their interpretations. > If those interpretations are some compound types, their components should be > available through var.somePropertyName or var[123], etc.
That should be very trivial to implement. The example on the front page of the wiki should be all the guidance needed, although you might like to play with cache settings and the like. > Are there some important incompatibilities? From the projects' trac it seems > the implementation is pretty complete when it comes to features that are > applicable in a RESTful approach. If I see correctly, you don't mention > <ui:fragment /> tag on your wiki. Is it available? I haven't really followed Facelets since making the port, and I've never actually ported any Facelets projects over. As far as the ui: taglib is concerned I appear to be missing ui:remove (perhaps this was added after I ported) and ui:component was removed because it was JSF specific (and thus ui:fragment was also removed). Aside from those changes, it's pretty much the same code as Facelets so should be mostly compatible. > Well, in the end I would really like to say: thank you, thank you, thank you. > I really spent a gazillion hours looking for some decent templating solution > that is previewable and isn't using some home-brew domain specific language > or isn't tightly coupled with some crappy stateful web framework. No problem - it's exactly why I made the port in the first place. Regards, Michael. ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2665143
