Subject: RE: Simple API for XSL? From: Tim McCune <timm@xxxxxxxxxxxxxxxx> Date: Wed, 17 Feb 1999 08:11:40 -0700 |
I went ahead and wrote an interface that lets us switch XSL processors by changing one line of code. The interface is pretty simple so far: public String process(Document xml, String stylesheetName) throws XSLProcessorImplException; I then wrote implementations of this interface for LotusXSL and XSLP. What other methods would be useful in such an interface? -----Original Message----- From: Lars Marius Garshol What should the API do here? What kind of functionality should it have? I can see some possibilities that might be both useful and practical: - starting the processing - receiving error events - some way of accessing the result tree (AFAIK first proposed by Paul Prescod on the Python XML-SIG mailing list a couple of days ago). This might take the form of SAX events or a DOM tree. This idea probably has some merit, since it would make it far easier to embed existing XSL processors as components in larger processing frameworks and applications. XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: Simple API for XSL?, Ed Nixon | Thread | Re: Simple API for XSL?, Tyler Baker |
Re: CSS and XSL, Paul Prescod | Date | Re: Simple API for XSL?, Tyler Baker |
Month |