That's exactly why Chris wrote what he wrote. You need to make sure JAXP's default XML parser is no longer the outdated Aelfred parser but Xerces. FOP always uses the default JAXP XML parser. WebSphere doesn't use Aelfred by default so that means you already replaced the default XML parser somehow. The WebSphere console should help you find out what exactly is on the classpath.
Jeremias Maerki On 04.10.2007 02:24:13 Kevin wrote: > Chris, > > Thanks for your help. I am not explicitly using that parser. Its getting > called > within the FOP code when I do that area tree -> PDF transform. > > Any suggestions. > > Thanks > Kevin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
