|
From: David K. <dav...@al...> - 2003-09-30 16:06:11
|
McDonald, Bruce wrote: > David, > > Ok, Lets find out exactly what the issue is - is it always the same configuration option that is failing or is some random option. Can you surround the getOptionList in XPathExtract with a try/catch and then dump the configuration data from the pipelinestage stage and the attributes on the document. Hmm...let's see...I managed to trigger a failure twice in the same stage with the same two input documents. The stage configuration is: # XPath Extract - get the file_id attribute extract_fid.stageType=XpathExtract extract_fid.nextStage=file_writer extract_fid.failOnError=false extract_fid.errorStage=error extract_fid.XPath.orig_file_id=/newsitem/@file_id And the (horribly unformatted) dump of doc attributes and pipeline stage configuration are attached for both runs. Initial observation (I think): - failOnError is null, as is - errorStage, as well as - XPath.orig_file_id in both cases. Correct? Any clues from that? > regards, > Bruce. David |