XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Conferences Close Tree View
+ Stylus Studio Feature Requests (1168)
- Stylus Studio Technical Forum (14390)
-> + API or web version (2)
-> + How to use Saxon for X16 on WI... (9)
-> + Error in SS X14 syntax highlig... (2)
-> + Option not available (2)
-> + XML Diff functionality and sor... (3)
-> + Convert Oagis XML file to TXT (4)
-> + DataDirect xqresultsequence is... (2)
-> - xfile Legacy file format suppo... (1)
-> + TPFDF (3)
-> + Help needed with SLSRPT - EDIF... (2)
-> - keeps crashing after I try and... (1)
-> + Can SS do this? (14)
-> - CargoImp support (1)
-> + No Preview Displayed - File is... (3)
-> - Stylus Studio X16 build 1974l ... (1)
-> + Help! Help!Help! Regading form... (2)
-> + FileNotFoundException generati... (6)
-> + FO External Graphic Producing ... (2)
-> + Use of Java methodes (4)
-> + get generated XQuery output on... (2)
-- [1-20] [21-40] [41-60] Next
+ Website Feedback (244)
+ XSLT Help and Discussion (7583)
+ XQuery Help and Discussion (1941)
+ Stylus Studio FAQs (159)
+ Stylus Studio Code Samples & Utilities (363)
+ Stylus Studio Announcements (113)
Topic  
Postnext
Cory MathisSubject: 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?

Postnext
Ivan PedruzziSubject: XML Pipeline Question
Author: Ivan Pedruzzi
Date: 16 Jan 2007 05:34 PM
Hi Cory,

Did you look at video tutorial?
http://www.stylusstudio.com/videos/pipeline2/pipeline2.html

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.

Hope this helps
Ivan Pedruzzi
Stylus Studio Team

Postnext
Cory MathisSubject: XML Pipeline Question
Author: Cory Mathis
Date: 17 Jan 2007 01:04 PM
All files are local but when we use MSXML4 as the pipeline execution framework, we get this message:

"java.net.SocketException: Network is unreachable: connect
Error: XSLT processing by XSLT block 'scenario_1.xsl' failed: java.net.SocketException: Network is unreachable: connect"

When we process with Stylus Studio execution framework, we do not get this error. We must use MSXML to process the XSLT.

Any ideas?

Postnext
Alberto MassariSubject: XML Pipeline Question
Author: Alberto Massari
Date: 17 Jan 2007 02:13 PM
Hi Cory,
could you send all the relevant files (.pipeline and .xslt) to stylus-field-report@progress.com?

Thanks,
Alberto

Postnext
Kurt MartinSubject: XML Pipeline Question
Author: Kurt Martin
Date: 17 Jan 2007 03:33 PM
Hi Alberto,

I am working with Cory on this issue.

java.net.ConnectException: Connection timed out: connect
Error: XSLT processing by XSLT block 'scenario_1.xsl' failed: java.net.ConnectException: Connection timed out: connect

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.

Thanks,

Kurt


UnknownKMart.zip
XSLT and Pipeline files

Postnext
Alberto MassariSubject: Re: XML Pipeline Question
Author: Alberto Massari
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.

Hope this helps,
Alberto

Posttop
Kurt MartinSubject: Re: XML Pipeline Question
Author: Kurt Martin
Date: 18 Jan 2007 11:47 AM
The .NET parser errors out too!

Any idea as to an ETA for this update? If it will be more than a week, we will have to look at a different solution.

Thanks,

Kurt

   
Download A Free Trial of Stylus Studio 6 XML Professional Edition Today! Powered by Stylus Studio, the world's leading XML IDE for XML, XSLT, XQuery, XML Schema, DTD, XPath, WSDL, XHTML, SQL/XML, and XML Mapping!  
go

Log In Options

Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.