Within the EcsServletElement class, I found the following comment:
* NOTE: The use of Ecs for aggregating portlet content is deprecated!
* This utility class will be removed once we don't have the ecs
* dependency any more.
I gather that the EcsServletElement should no longer be used. But I
like the idea of externalizing content generation to a JSP, so that a
non-developer can change the content of a portlet using the HTML/JSP
design tool of their choice. Is there another way to accomplish this?
I looked at the ServletInvokerPortlet that comes with Jetspeed, and it
also uses EcsServletElement. What alternatives do I have?
Background info on how I arrived at this question, for those interested:
I created a portlet that attempts to externalize content generation to
a JSP, as shown in the "How to Write a Portlet" doc. This portlet
creates an org.apache.ecs.ElementContainer, puts an EcsServletElement
into the ElementContainer, and returns the ElementContainer. When I run
this portlet, the content from my external JSP is generated, but it
appears above all of the portlets, instead of inside my portlet. I
simplified my JSP as much as possible, confirming for myself that it
wasn't an HTML problem. I then returned the EcsServletElement instead
of the ElementContainer (both of which extend ConcreteElement), and
still my portlet content is displaying before the portlets table.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
