[RESOLVED] How do I find why a xsltprocessor->transformToDoc failed?

tcarnes

I have about 8,000 xml files that I need to transform to html for display in a browser. The transformToDoc function is returning a "false" for about 1,000 of them and I need to find out why.

Is there a way to find out what the error was, why the transformation failed?

My code is:

$xsl = new DOMDocument();
$xsl->load('http://www.fda.gov/oc/datacouncil/stylesheets/spl/spl.xsl');
$proc = new XSLTProcessor();
$proc->importStylesheet($xsl);
$xml = new DOMDocument();
$xml->load($xmlFile);
$domTranObj = $proc->transformToDoc($xml);
if ($domTranObj === false)
{
	$isGood = 0;
	$error = 'XML Transformation Failed';
	// How do I find out why the transformToDoc failed?
	$numbad++;
}

Would someone help point me in the right direction? How do I find out why the transformToDo failed?
Terry

NogDog

I don't see anything in the manual suggesting any sort of built-in error-tracking within that class, so all I can suggest is to ensure all error reporting or logging is on and see if it sheds any light on the subject:

<?php
ini_set('display_errors', 1); // set to 0 for production version
error_reporting(E_ALL);

tcarnes

I did as Nogdog suggested and received the following errors:

Warning: XSLTProcessor::transformToDoc() [function.XSLTProcessor-transformToDoc]: runtime error: file http://www.fda.gov/oc/datacouncil/stylesheets/spl/spl-common.xsl line 803 element attribute in C:...\xml-test.php on line 78

Warning: XSLTProcessor::transformToDoc() [function.XSLTProcessor-transformToDoc]: xsl:attribute : node already has children in C:...\xml-test.php on line 78

I read elsewhere that "node already has children" is a recoverable error and that "the system is allowed to report it (and die) or just silently ignore the offending instruction."

Is there a way I can get transformToDoc to silently ignore the offending instruction?

CoderDan

I had similar issues when I was last working on xslt, and I ended up just making sure the xslt was 100% valid (added it to a sample xml output header as the stylesheet and just kept tweaking it and refreshing it in firefox for clientside transform till it was happy)
I never found any way to make the php transformer more lenient with errors.
I guess this isn't really any help, but I do reccomend trying to fix the xslt over changing the implementation.

tcarnes

CoderDan;10916029 wrote:
I do recommend trying to fix the xslt over changing the implementation.

Ah, there's the rub! I'm dealing with government files that I have little control over.

How can I modify XSLTProcessor so that it will ignore the warning and not just return false?

CoderDan

tcarnes;10916053 wrote:
Ah, there's the rub! I'm dealing with government files that I have little control over.

How can I modify XSLTProcessor so that it will ignore the warning and not just return false?

Oh what fun... I hate those kinds of jobs. Wish I could help on that one.

perhaps you could try an alternate implementation like http://sourceforge.net/projects/xslt2processor/

tcarnes

Thanks for the pointer to XSLT2Processor. I ended up using it with AltovaXML. I had trouble initially getting the COM interface to work with PHP and ended up using the .NET interface writing a VB program to do the transformations. Turns out that the problem that pushed me to VB might not have been related to the COM interface after all.

But eventually, I was able to get everything transformed. Thank you for your help!

Terry