|
From: Colin S. <col...@ex...> - 2005-09-01 00:37:13
|
InternalResourceView just does a RequestDispatcher.forward (or include in some cases). This is exactly how you are suppose to get to the JSP engine. There is no 'more effiicient' or direct mechanism. Regards, Colin Andreas Schildbach wrote: > Hello everyone, > > Please consider the InternalResourceView, which re-routes a request > through the whole "webapp pipeline" (filters, JSP servlet...) again. > > Wouldn't it be possible to somehow plug directly to JSP rendering for > JSP based views? > > The main benefit I would expect is that maybe the model could be > exposed as page scope attributes rather than request attributes, so > they would be local to the page only. > > The other benefit would be perhaps a performance gain. I'm a bit > suspicious that in a large application with many include fragements > and such, a lot time is wasted in the "pipeline"... > > What do you think? Would it be possible? > > Regards, > > Andreas > > > > ------------------------------------------------------- > SF.Net email is Sponsored by the Better Software Conference & EXPO > September 19-22, 2005 * San Francisco, CA * Development Lifecycle > Practices > Agile & Plan-Driven Development * Managing Projects & Teams * Testing > & QA > Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer |