XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
search
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Home » Boards » Stylus Studio Developer Network » Stylus Studio Technical Forum » Archiving output from conversion
Conferences Close Tree View
+ Stylus Studio Feature Requests (1192)
- Stylus Studio Technical Forum (14621)
-> - Stylus Studio - Registrar en o... (1)
-> + Stylus Studio - Registrar en o... (2)
-> + Can a pipeline send a file by ... (2)
-> + After Updateing WIN10 to WIN11... (12)
-> + Where do I add the custom java... (3)
-> + Where is the Diagram tab? (5)
-> + Applying XSLT to Word DOCX/XML (2)
-> - CSV conversion via ConvertToXM... (1)
-> + Text symbols in SS not same as... (4)
-> + Exposing xquery as webservice ... (6)
-> + Syntax Identifier (2)
-> + Saving a Converted XML as an X... (5)
-> + Output document cannot be pars... (4)
-> - Archiving output from conversi... (1)
-> + EDIFACT guideline from Stylus ... (3)
-> + CSV file putting all the data ... (5)
-> + Can't install Home version 64b... (5)
-> + presale - Can I covers this sc... (5)
-> + Problem with UNB (5)
-> + Splitting EDIFACT files pipeli... (4)
-- [1-20] [21-40] [41-60] Next
+ Website Feedback (249)
+ XSLT Help and Discussion (7625)
+ XQuery Help and Discussion (2016)
+ Stylus Studio FAQs (159)
+ Stylus Studio Code Samples & Utilities (364)
+ Stylus Studio Announcements (113)
Topic  
Posttop
Bruce CantorSubject: Archiving output from conversion
Author: Bruce Cantor
Date: 25 Jan 2022 12:26 PM
Hi

I was wondering if there might be a better solution to this challenge that I often have:

We often convert our internal XML files to other XML file formats.

We would like to keep a copy of the output in an archive folder, making it easier to troubleshoot problematic files later.

A typical simple pipeline would then consist of a pipeline input node, a xslt node and the two pipeline output nodes.

I have noticed that forking output from a xslt node to a output node is troublesome.

I am not sure about the behaviour, but usually one ore both output nodes ends up not getting output.

It can be solved by adding a xslt node that does nothing else than copy the previous document output and the take archive and output from the two different nodes. This works, but then a redundant xslt script is added to the transformation.

I found that if I use a XML parser node in SS the output is parsed correctly to both nodes, but not sure if this is more or less ressource demanding. Or if it works in Pipeline server.

Attached is a visual representation of the question, the different scenaries represented by each input node.


UnknownvisualOfIssue.pipeline
Visual of question
   
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.