Hi Erik ! I meant 'legacy' for u, the one u were using w/ 1.3 and that was working for u.
for ur concern, one way I would think of is to launch the xslt ant task inside a java call and fork it, so that u are able to then set ur classpath and for this task only (but looks to me u'll have to do it everywhere u want to access this parser and not the java one). seb. Erik Putrycz wrote: > I did not knew Xalan2.3 was legacy ;) > I know the bootclasspath trick works but I was looking for a way to set it > fully inside ant rather than setting java options. > I have been trying some tricks with the contextclassloader but without > success that far... > > Erik. > > ----- Original Message ----- > From: "Sebastien Blanc" <[EMAIL PROTECTED]> > To: "Ant Developers List" <[EMAIL PROTECTED]> > Sent: Thursday, March 20, 2003 7:16 PM > Subject: Re: xml parser and classloading > > > did u try modifying ur ANT bootclasspath startup script to have ur legacy > > parser before the jdk1.4 one ? > > seb. > > > > Erik Putrycz wrote: > > > > > I am currently having some troubles with the xslt/style task and I > > > experience some bug due to the XML parser (Xalan2 bundled with jdk1.4). > > > The XML parser included with jdk1.4 suffers from some bugs and it is a > pain > > > to force another XML parser. > > > Has anyone investigated this issue and maybe allow a way inside ant to > > > specify the classpath and classloader used for loading the xml parser ? > > > > > > Erik. > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED]
