cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From K Karun <kka...@us.oracle.com>
Subject Re: XSLT API Proposal
Date Sat, 05 Feb 2000 08:44:08 GMT

Scott Boag/CAM/Lotus wrote:
> Right, and it seems a bit complicated.  I like the notion of a
> XSLTSourceDocument. How about:
> 
> XSLTProcessor processor = new VendorProcessor();
> XSLTSourceDocument source
>    = processor.getSourceDocument(new XSLTInputSource(xxx));
> Transform transform = source.getAssociatedStylesheet();
> processor.setParameter(name, value);
> transform.process(processor, source,
>      new XSLTResultTarget(xxx));
> 
> comments?

Hmmm... I don't see any advantage of having XSLTSourceDocument. The
function getAssociatedStylesheet() can belong to XSLTInputSource. Both
XSLTInputSource and XSLTSourceDocument as classes, and may be they can
be combined. 

XSLTProcessor processor = new VendorProcessor();
XSLTInputSource source = new XSLTInputSource(xxx);
XSLTInputSource stylesheet = source.getAssociatedStylesheet();
Transform transform = processor.createTransform(stylesheet);
processor.setParameter(name, value);
transform.process(processor, source, new XSLTResultTarget(xxx));

Any ideas/comments?

Thanks
Karun

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
K. Karun                          Project Lead, Java XML Components
CORE and XML Development          Phone: (650) 506 9874
Server Technologies               Fax:   (650) 506 7203
Oracle Corporation                http://technet.oracle.com/tech/xml
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Mime
View raw message