Hi All, I've integrated Spring with Magnolia before and got it so that the Spring dispatcher servlet would get a request & action it via a Controller and then Magnolia would render the page, thus getting the best of both worlds. However, I did this by adding filter bypasses to the CMSfilter and others which wasn't too pretty.
Also, I had trouble when we wanted users to upload photos - Spring would get the request, read the attached photo from the request & process it and then dispatch back to Magnolia to render. This time round the Magnolia Multipart filter would intercept the request and try and process it with a 500 error, as the input stream for the binary data had already been read. We got around this but it wasn't nice. So I'd like to have a go at integrating Spring in a better manner. My idea this time is to create a Magnolia filter very similar to the Servlets filter that would dispatch the flow to the Spring Dispatcher servlet. Then however it would continue processing within the Magnolia filter chain unlike the Servlets filter. As part of the continuation it would work out the path within the CMS that the view corresponds to. Does this seem like a workable solution ? My concern at present is that misconfiguration could result in bypassing the ACLs for pages as the Spring dispatcher may get called after the Security filter but then the view that gets rendered could be a protected page depending on the Controllers response. All thoughts / comments gratefully received. Jon. ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
