Rapha�l Luta wrote:
<snip>
> Currently the XMLPortletController has the major drawback that it requires
> well-formed XML to output anything, thus it breaks with ECS code outputting
> HTML instead of XHTML, and may break with FilePortlet...
> I really think all portlets should be forced to output XML compliant
> markup in order to be able to switch controller at will. I assume it's only
> a configuration issue in ECS but I don't have any satisfactory solution for
> FilePortlet.
<snip>
I know. This is probably something I am going to address in 1.2. (the
next version will probably be out tuesday and be 1.1). I agree. The
problem is the FileServerPortlet. We could possibly CDATA the output
from the Portlet and include it raw in our transform. This would work
for good web browsers (Netscape included :) as long as we didn't want to
do XHTML validation some day.
I would like to just replace the stock PortletController with one that
is XSP. This makes more sense and we
can have dynamic content and static customization in an easy manner.
The current problem is that XSP doesn't work under Jetspeed. I spent a
lot of time trying to get this to work but there are still some bugs.
:( Has to do with the fact that Cocoon isn't acting as a Servlet.
Kevin
--
Kevin A Burton ([EMAIL PROTECTED])
http://relativity.yi.org
Message to SUN: "Please Open Source Java!"
"For evil to win is for good men to do nothing."
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
