Frank Ritzmann wrote: >hallo jetspeed-users, > >I heard, that ecs won't be supported by jetspeed any longer. >would this mean, that there is no EcsServletElement anymore? > >to me this element is the easiest way to integrate JSPs in portlets by just returning >the EcsServletElement as a ConcreteElement. > There are scalability problems in the ECS architecture. If the system is preparing pages simultaneously for a lot of users it will have to create and manipulate trees of ECS objects, which will be discarded later. While some of these trees can be cached, it is difficult for dynamic content. So memory and garbage collection soon become a problem.
So, a decision was made to use streaming solutions, where the JSP is handled the response stream and it writes to it. For low volume applications you can use solutions similar to ECS, but the architecture is cleaner if you use streams for aggregation. (Except when an error happens in the middle of the page generation process. :-) > >using the JspPortlet would mean, that I have to set my parameter beans into the >session within my JSP but that is not like MVC. > >if this element is not available anymore, I will think about copying the getContent >of JspPortlet and adding my parameter controlling and identifying the active portlet >for not losing my actual content when a user interacts with another portlet. > >thank you for reading and answering >Frank Ritzmann > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
