Cart
|
Home > Online Product Documentation > Table of Contents > Using Apache FOP to Generate NonPDF Output Using Apache FOP to Generate NonPDF OutputThe Apache FOP included with Stylus Studio is configured to output PDF. To use this FOP to generate some other type of output:
1. Open the stylesheet whose results you want to postprocess with the Apache FOP.
2. Create or open a scenario in which to do the post-processing. See
Creating a Scenario. Stylus Studio displays the
Scenario Properties dialog box.
3. In the
Scenario Properties dialog box, click the
Post-process tab.
4. Select
Custom post-process.
5. In the
Command line field, enter something like the following:
Modify this sample command line according to where Stylus Studio is installed and what kind of output you want the FOP to generate. The last option,
6. In the
Generated file extension field, specify the extension that indicates the type of output you want. For example, specify
.txt if you want the FOP to generate a text file.
7. If there is additional path information that the FOP will require to execute successfully, type it in the
Additional path field.
8. Click OK.
|
Building Web Services With Stylus Studio
This video demonstration shows you how to use Stylus Studio's Web Service call composer to locate a WSDL file on the Internet, inspect, create SOAP envelope, invoke and inspect Web service data.
Data Integration Tools: Using the Stylus Studio XML Pipeline to Visually Integrate and Publish Data
Data Integration Tools from Stylus Studio include a visual pipeline editor, support for non-XML data sources, scalable data integration components, cross-language debugging and Java code generation. Try it now.
Validating X12 Documents with XML Schemas
Either before or after transforming X12 EDI content, generated XML Schemas will make sure that we have all of the necessary components, our codes are all according to the standard codelists, and every little delimiter is in the right place.
Validating EDIFACT Documents with XML Schemas
Either before or after transforming EDIFACT content, generated XML Schemas will make sure that we have all of the necessary components, our codes are all according to the standard codelists, and every little delimiter is in the right place.
