Subject:XML Pipeline Question Author:Cory Mathis Date:16 Jan 2007 02:49 PM
We have a series of seven XSLTs. We need the output from the first XSLT as an input to the second XSLT, the output from the second to the third, etc. We have been attempting to do this in the pipeline editor and have been unable to get past the first XSLT. How do you configure this in the pipeline editor?
One way to proceed is add the XSLT documents to the Stylus Studio project then create a new pipeline document then drag and drop the XSLTs into the pipeline canvas
At this point you should be able to connect the output port of one XSLT to the input port of another XSLT.
javax.xml.transform.TransformerException: java.net.ConnectException: Connection timed out: connect
at org.apache.xalan.transformer.TransformerImpl.fatalError(TransformerImpl.java:744)
at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:718)
at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1179)
at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1157)
at com.exln.stylus.CXalanDriver.doProcessing(CXalanDriver.java:133)
at com.exln.stylus.CProcessorDriver.process(CProcessorDriver.java:98)
Caused by: java.net.ConnectException: Connection timed out: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at sun.net.NetworkClient.doConnect(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.<init>(Unknown Source)
at sun.net.www.http.HttpClient.New(Unknown Source)
at sun.net.www.http.HttpClient.New(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
at java.net.URL.openStream(Unknown Source)
at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source)
at org.apache.xerces.impl.XMLEntityManager.startEntity(Unknown Source)
at org.apache.xerces.impl.XMLEntityManager.startDTDEntity(Unknown Source)
at org.apache.xerces.impl.XMLDTDScannerImpl.setInputSource(Unknown Source)
at org.apache.xerces.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xml.dtm.ref.DTMManagerDefault.getDTM(DTMManagerDefault.java:478)
at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:661)
... 4 more
---------
java.net.ConnectException: Connection timed out: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at sun.net.NetworkClient.doConnect(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.<init>(Unknown Source)
at sun.net.www.http.HttpClient.New(Unknown Source)
at sun.net.www.http.HttpClient.New(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
at java.net.URL.openStream(Unknown Source)
at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source)
at org.apache.xerces.impl.XMLEntityManager.startEntity(Unknown Source)
at org.apache.xerces.impl.XMLEntityManager.startDTDEntity(Unknown Source)
at org.apache.xerces.impl.XMLDTDScannerImpl.setInputSource(Unknown Source)
at org.apache.xerces.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xml.dtm.ref.DTMManagerDefault.getDTM(DTMManagerDefault.java:478)
at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:661)
at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1179)
at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1157)
at com.exln.stylus.CXalanDriver.doProcessing(CXalanDriver.java:133)
at com.exln.stylus.CProcessorDriver.process(CProcessorDriver.java:98)
This happens whenever we choose ANY XSLT processor (under Pipeline Scenario Properties) other than the Stylus Studio XSLT processor. We are taking advantage of the way MSXML handles recursive node handling, so when we use MSXML, processing usually takes about 6 seconds on average to process. If we use other processors, it can take up to an hour (when we run each XSLT separately outside the pipleline editor).
Attached are the XSLT and pipeline files you requested.
Subject:Re: XML Pipeline Question Author:(Deleted User) Date:18 Jan 2007 04:31 AM
Hi Kurt,
you are right, it looks that the pipeline runner is ignoring the
MSXML 4 option specified in the pipeline. We are working on a fix for
this problem; in the meanwhile you can try selecting ".NET 1.x" that
should give you the same optimizations of MSXML 4.