Jan 22nd, 2008, 12:11 PM
How would you implement a portal approach?
I've got a portal/CMS/application integration question:
The prerequsites are:
-Friendly URL / arbritrary URL mapping based on a "propietary" (e.g non-spring based) system - I guess I can fix this by implementing/extending an HandlerMapping.
-Merging of application content (e.g. spring controllers + view in JSTL) with static content - but NOT in the application controller/JSP-views. I'll try to explain: For a given request URL - I'll receive a list of static content files which shold be written to the servlet request output buffer - a long with URLs to spring - I want to merge this with the output from one or more controllers. How can this be done? I've tried to add a defaultHandler to the HandlerMapping which first writes the static content to the outputbuffer, and then fowards:/to/the/controller/url - and writing out the rest in a HandlerInterceptor.postHandle() - but I fall into problems because the output buffer has already been written to.
-Separation of the templating (e.g. merging of static content) with the applicaiton data (e.g. forwarding a given URL to a controller.
E.g. the merging of static content should be "invisible" for Controller implementers.
Another totally different and spring-less approach for the merging of content would be to do this in a filter - much like the sitemesh/decorator approach.
I've also been looking into making a custom View implementation - and handle all the merging in the rendering of the View - but this would tie our users to a propietary view implementation.
Any suggestions / views / good pointers for this case?