+1 for using Componentizing XSLTProcessor.
Thanks,
dims
--- Ovidiu Predescu <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I'm working on an extension logicsheet, and perhaps a transformer,
> which requires the use of the XSLT processor. Unfortunately the XSLT
> processor is not available as a component, as the XML parser is.
>
> So I went ahead and re-factored the TraxTransformer: I moved the XSLT
> functionality into a new component class, that conforms to the
> following interface:
>
> public interface XSLTProcessor
> {
> public void setSourceResolver(SourceResolver resolver);
>
> public TransformerHandler getTransformerHandler(Source stylesheet)
> throws ProcessingException;
>
> public void transform(Source source, Source stylesheet, Parameters params,
> Result result)
> throws ProcessingException;
> }
>
> The TraxTransformer now uses the XSLTProcessor component to do its
> XSLT processing.
>
> If people are interested in this, I will submit a patch later on,
> together with other enhancements I'm working on. More on these
> enhancements later on.
>
>
> Regards,
> --
> Ovidiu Predescu <[EMAIL PROTECTED]>
> http://orion.nsr.hp.com/ (inside HP's firewall only)
> http://sourceforge.net/users/ovidiu/ (my SourceForge page)
> http://www.geocities.com/SiliconValley/Monitor/7464/ (GNU, Emacs, other stuff)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
=====
Davanum Srinivas, JNI-FAQ Manager
http://www.jGuru.com/faq/JNI
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail
http://personal.mail.yahoo.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]