Saxon

Legacy ID: #6982667 Legacy Poster: David Lee (daldei)

I have found a new case where XdmDestination doesnt set the config in 9.1.0.6. This is a fairly convoluted case. If you need a program to reproduce it will likely take the whole program (xmlsh) but I can get you the source to reproduce this if you want it. Here's the stack trace TinyTree.addNode(short, int, int, int, int) line: 330 TinyTree.addDocumentNode(TinyDocumentImpl) line: 303 TinyBuilder.startDocument(int) line: 134 NamespaceReducer(ProxyReceiver).startDocument(int) line: 98 TreeReceiver.startDocument(int) line: 105 Util.writeXdmValue(XdmValue, Destination) line: 572 xed.run(List<XValue>) line: 211 xed(XCommand).run(List<XValue>, XEnvironment) line: 55 xed(XCommand).run(Shell, String, List<XValue>) line: 45 SimpleCommand.exec(Shell) line: 103 Shell.exec(Command) line: 395 Pipeline.exec(Shell) line: 112 .... config is null here : documentNumber = config.getDocumentNumberAllocator().allocateDocumentNumber(); I can work around this as I did in 9.1.0.5 using this method: private void setupDestination( XdmDestination dest ) { /* * TODO: Remove this extra code when Saxon is fixed * XdmDestinatin shouldn't need the configuration */ Configuration config = Shell.getProcessor().getUnderlyingConfiguration(); try { Receiver r = dest.getReceiver(config); PipelineConfiguration pipe = config.makePipelineConfiguration(); r.setPipelineConfiguration(pipe); ; } catch (SaxonApiException e) { ; } }