At 22:24 12/02/2001 +0100, you wrote:
>Raphaël Luta wrote:
><snip templating system description>
>>Point 1:
>>Should the Portlet API mandate that portlet only output full documents rather
>>than document fragments ?
>
>You mean here "proper" markup? This is more radical thant point 2. And
>impossible to enforce unless getWriter() disappears or expensive parsing
>is done with each portlet output. Even for our current SAX model, portlets
>otput documents that are acceptable as parts of the "global" page DTD. For
>instance <portlet>...</portlet> This is a document on its own, but is also
>part of the document that composes the page as a whole. Thus, for us this
>will be true. But I wonder if it can be true for everybody. Even for us,
>in some cases HTML fragments are bundled as CDATA (this will not work with
>WML) and passed through. We are trying to get rid of this, but it will not
>be easy until when most sites generate XHTML.
Yes this has a lot more consequences that Point 2, that's why I put it first :)
I know that requiring full document output will necessarily add a
post-processing step
after the portlet output so this will cost some performance.
But let's consider I'm a portlet writer writing a portlet that will
generate WML output
(WML is not as easily nestable as HTML). I will use the Portlet API and
plan that
my portlet will be run in several different portal implementations:
- one based on Turbine/Velocity
- one based on Cocoon 2
- one based on JSP/Struts
If I can't output full wml decks, what guidelines should I follow that make
sense for all
these portals ?
Personnally I can't find any, that's why I'm promoting the use of complete
documents
generation by the portlets.
--
Raphaël Luta - [EMAIL PROTECTED]
Vivendi Universal Networks - Services Manager / Paris
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/[email protected]/>
List Help?: [EMAIL PROTECTED]
