Raphael wrote:
> I'm not talking about "data XML markup" there, simply weel-formed XHTML,
WML
> or whatever.
> I think in many portal will want to post-process a portlet output.
> For example:
> in XHTML case to merge all <link> and <script> elements in the <head>
> of the aggregated document or to strip some "dangerous" tags.
> in WML: the portal will want to retrieve all the <title> elements for
building
> a navigation stack before linking to the complete portlet content.
> Using SAX events as the interface between portal and portlet makes this
activity
> both simple and efficient.
> It's easy to connect an output stream to a SAX parser so there's no loss
of
> generality only the performance hit of a parser if you use tools that
don't
> output directly SAX events. Since I think portal will almost always need
to
> parse the portlet response, it's not an issue IMO.
I tend to agree with this, not only for the cases mentioned, but also for
simple cases where syndicated content is being used. The companies which
provide news and other content feeds actually send you quite a mess, with
unmatched tags, etc. Even when you request XML data from them, they dump
a whole bunch of bad HTML tags into a CDATA element, which makes it very
hard to transform the XML into anything else.
Carol
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://marc.theaimsgroup.com/?l=jetspeed>
Problems?: [EMAIL PROTECTED]
