Hi Stefan, Steve, I have been looking at XSLTProcess and have started bringing XMLValidate up to paar. Should XMLValidate handle the factory configuration exactly the same way as the XSLT task?
I am using an XSLTProcess.Factory, however, should I rework XMLValidate so that it configures the Liason in the same as XSLTProcessor ? viz, XSLT uses a "processor" attribute and XMLValidate uses just a "className", where "processor" can be "trax" etc. Or should XMLValidate provide both mechanisms for setting the processor in the future? Hope I am not too far off the track. Cheers, Nick > -----Ursprungliche Nachricht----- > Von: Stefan Bodewig [mailto:[EMAIL PROTECTED] > Gesendet: Montag, 9. September 2002 09:25 > An: [EMAIL PROTECTED] > Betreff: Re: cvs commit: > jakarta-ant/src/main/org/apache/tools/ant/taskdefs/optional > XMLValidateTask.java > > > I don't like this patch, sorry. > > (1) XMLValidate used to compile fine with JDK 1.1, now all the 1.1 > collection classes have been replaced with 1.2 classes for no gain. > > (2) I've twiced asked (Nick on this list) to rework this patch to > allow configuring the factory in the same way Stephane has modified > <xslt> so that we have a single consistent way to do so (and I think > <xslt>'s way is superior). > > Stefan > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
