[xep-support] Re: XSL-FO validation issues on Win7/64bit

From: Kevin Brown <kevin@renderx.com>
Date: Wed Feb 16 2011 - 09:45:51 PST

My mistake Dave, it is required for validation but as Michael Sulyaev points
out validation is a parsing step run by XT. So it could be XT or it could be
in the default SAX parser used by XT.


-----Original Message-----
From: Jan To¹ovskı [mailto:j.tosovsky@gmc.net]
Sent: Wednesday, February 16, 2011 12:14 AM
To: kevin@renderx.com; RenderX Community Support List
Subject: RE: [xep-support] Re: XSL-FO validation issues on Win7/64bit

If you mean something like this:
java -Xss2m -Xmx1024m -cp
com.renderx.xep.XSLDriver -DCONFIG=C:\db\progs\xep\xep.xml

it doesn't help. I am getting the same errors.
I'll prepare some not confidential data for your further investigation.


-----Original Message-----
From: xep-support-bounces@renderx.com
[mailto:xep-support-bounces@renderx.com] On Behalf Of Kevin Brown
Sent: Wednesday, February 16, 2011 2:26 AM
To: 'RenderX Community Support List'
Subject: [xep-support] Re: XSL-FO validation issues on Win7/64bit

OK, here is my thoughts on this:

> java -Xss2m -Xmx1024m -cp C:\db\progs\xep\lib\xep.jar
com.renderx.xep.XSLDriver -DCONFIG=C:\db\progs\xep\xep.xml

The failure in all your applications I believe is a failure in 64bit Java
XSL transform.

Use Saxon, please .... and test again.

The above command explicitly EXCLUDES any transformer from the Classpath and
therefore it is using the default Java transform XALAN -- and this is where
the error lies I believe - 64bit transform with XALAN in memory.

(*) To unsubscribe, please visit http://lists.renderx.com/mailman/options/xep-support
(*) By using the Service, you expressly agree to these Terms of Service http://w
Received on Wed Feb 16 09:46:07 2011

This archive was generated by hypermail 2.1.8 : Wed Feb 16 2011 - 09:46:15 PST