XSL Processor Parser C++

I want to get a XSL Processor Parser C++
but, Now XSL Processor is a java, pl/sql version.
I want to know when a XSL Processor Parser C++ is coming soon..
null

Patty Bluhm (guest) wrote:
: I'm interested in this, also and it doesn't appear to be
: available, yet. Do you have an updated date?
: Oracle XML Team wrote:
: : The C++ version will be available by the end of the month.
: : Oracle XML Team
: : http://technet.oracle.com
: : Oracle Technology Network
It should be available by the end of next week.
Oracle XML Team
http://technet.oracle.com
Oracle Technology Network
null

Similar Messages

Xsl processor and xml parser?

Hello,
Can someone tell me wich is the xsl processor and the xml parser used by Livecycle ES? And their versions?
Thank you

XML Parser parses the text representation of an XML 1.0-compliant document to make the document's information set -- elements, attributes, text, comments, processing instructions, namespace declarations -- available for access to a comptuter program.
Without a parser, a program cannot make heads or tails of the tree of information contained in your tags.
An XSL Processor is a program that takes an XML Document as input, along with an XSLT transformation definition (also known as a stylesheet), and effects the transformation of the source document as instructed by the stylesheet. This might mean transforming:
<ROWSET>
<ROW>
<ENAME>Steve</ENAME>
</ROW>
</ROWSET>
into
<human-resources>
<employee name="Steve"/>
</human-resources>
or alternatively into:
<html>
<body>
<b>Steve</b>
</body>
</html>
In both cases, the source XML document
is the same, but when transformed by
one stylesheet, it might become
the <human-resources> XML document.
When transformed by another stylesheet,
it can become pretty HTML.
To put the two terms in context, an XSL processor uses an XML parser to read the source XML document and to read the XSL transformation definition (aka stylesheet) -- since it, too, is an XML document -- and then it proceeds to transform the source into the target.

Xsl:output function fully implemented in XSL-processor?

I'm using XSL-processor as contained in the XML-parser version 2.0.2 in C.
When changing the referring DTD of an incoming XML-message with following XSL-stylesheet
<xsl:output method="xml"/>
<xsl:output ommit-xml-declaration="no"/>
<xsl:output standalone="no"/>
<xsl:output doctype-system="someOther.dtd"/>
nothing seems to happen.
Is <xsl:output> already fully implemented in this C-version of the XSL-processor?
Erwin

Hi,
The xsl:output is not yet implemented. This was specified in the README file.
Thanks,
Oracle XML Team
null

Converting XML in WML using XSL Processor from XMLParser v2

When trying to concert an XML doc into WML, it seems like the XSL Processor is removing some WML tags. Below are the XML doc and XSL doc I am using :
The XML DOC
<?xml version="1.0"?>
<ROWSET>
<ROW id="1">
<NAME>RestaurantName</NAME>
<ADDRESS>RestaurantAddress</ADDRESS>
<PHONE_TYPE>Fixed</PHONE_TYPE>
<PHONE>0112345678</PHONE>
<PRICE>60</PRICE>
<MENU>Salad, Pizza</MENU>
<DESCRIPTION>Very good restaurant</DESCRIPTION>
</ROW>
<ROW id="2">
<NAME>SecondRestaurantName</NAME>
<ADDRESS>SecondRestaurantAddress</ADDRESS>
<PHONE_TYPE>Fixed</PHONE_TYPE>
<PHONE>0187654321</PHONE>
<PRICE>60</PRICE>
<MENU>Salad, Fish</MENU>
<DESCRIPTION>Godd restaurant</DESCRIPTION>
</ROW>
</ROWSET>
The XSL DOC
<?xml version="1.0"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="/">
<WML>
<CARD>
<xsl:apply-templates/>
</CARD>
</WML>
</xsl:template>
<xsl:template match="ROWSET">
<xsl:for-each select="ROW">
<xsl:value-of select="NAME"/>
<xsl:value-of select="ADDRESS"/>
Phone : <xsl:value-of select="PHONE"/>
Price of the menu : <xsl:value-of select="PRICE"/>
You can order : <xsl:value-of select="MENU"/>
<xsl:value-of select="DESCRIPTION"/>
</xsl:for-each>
</xsl:template>
</xsl:stylesheet>
The
tag are removed by the XSL Processor ; In fact it seems that any tag contained within <xsl:template match="ROWSET"> and </template> is removed. This does not occurs with other XSL processor (such as lotusxsl).
Is there something I'm doing wrong ??

Your examples works correctly for me using the XSLT engine that comes with release 2.0.2.6 of the Oracle XML Parser "v2" for Java.
Are you working with this latest release?

XDK9.2.0.2, pb with JAXP and XSL Processor

Hello,
I'm using XDK 9.2.0.2 and I try to use JAXP.
I have a difference between using the Oracle XSL processor directly and through JAXP.
Through JAXP, the processor don't care about the xsl:outpout encoding attribute !
Why ?
It take care of method, indent, ... but not encoding !
I try to set the property with : transformer.setOutputProperty(OutputKeys.ENCODING, "iso-8859-1");
It works but I don't want to do that this way !
TIA
Didier
sample (from XSLSample2):
/* $Header: XSLSample2.java 07-jan-2002.02:24:56 sasriniv Exp $ */
/* Copyright (c) 2000, 2002, Oracle Corporation. All rights reserved. */
* DESCRIPTION
* This file gives a simple example of how to use the XSL processing
* capabilities of the Oracle XML Parser V2.0. An input XML document is
* transformed using a given input stylesheet
* This Sample streams the result of XSL transfromations directly to
* a stream, hence can support xsl:output features.
import java.net.URL;
import oracle.xml.parser.v2.DOMParser;
import oracle.xml.parser.v2.XMLDocument;
import oracle.xml.parser.v2.XMLDocumentFragment;
import oracle.xml.parser.v2.XSLStylesheet;
import oracle.xml.parser.v2.XSLProcessor;
// Import JAXP
import javax.xml.transform.*;
import javax.xml.transform.dom.*;
import javax.xml.transform.stream.*;
public class XSLSample2
* Transforms an xml document using a stylesheet
* @param args input xml and xml documents
public static void main (String args[]) throws Exception
DOMParser parser;
XMLDocument xml, xsldoc, out;
URL xslURL;
URL xmlURL;
try
if (args.length != 2)
// Must pass in the names of the XSL and XML files
System.err.println("Usage: java XSLSample2 xslfile xmlfile");
System.exit(1);
// Parse xsl and xml documents
parser = new DOMParser();
parser.setPreserveWhitespace(true);
// parser input XSL file
xslURL = DemoUtil.createURL(args[0]);
parser.parse(xslURL);
xsldoc = parser.getDocument();
// parser input XML file
xmlURL = DemoUtil.createURL(args[1]);
parser.parse(xmlURL);
xml = parser.getDocument();
// instantiate a stylesheet
XSLProcessor processor = new XSLProcessor();
processor.setBaseURL(xslURL);
XSLStylesheet xsl = processor.newXSLStylesheet(xsldoc);
// display any warnings that may occur
processor.showWarnings(true);
processor.setErrorStream(System.err);
// Process XSL
processor.processXSL(xsl, xml, System.out);
// With JAXP
System.out.println("");
System.out.println("With JAXP :");
TransformerFactory tfactory = TransformerFactory.newInstance();
String xslID = xslURL.toString();
Transformer transformer = tfactory.newTransformer(new StreamSource(xslID));
//transformer.setOutputProperty(OutputKeys.ENCODING, "iso-8859-1");
String xmlID = xmlURL.toString();
StreamSource source = new StreamSource(xmlID);
transformer.transform(source, new StreamResult(System.out));
catch (Exception e)
e.printStackTrace();
My XML file :
<?xml version="1.0" encoding="ISO-8859-1"?>
<ListePatients>
<Patient>
<Nom>Zeublouse</Nom>
<NomMarital/>
<Prinom>Agathe</Prinom>
</Patient>
<Patient>
<Nom>Stick</Nom>
<NomMarital>Laiboul</NomMarital>
<Prinom>Ella</Prinom>
</Patient>
<Patient>
<Nom>`ihnotvy</Nom>
<NomMarital/>
<Prinom>Jacques</Prinom>
</Patient>
</ListePatients>
my XSL file :
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
<xsl:output method="html" omit-xml-declaration="yes" indent="yes" encoding="ISO-8859-1"/>
<xsl:template match="*|/"><xsl:apply-templates/></xsl:template>
<xsl:template match="text()|@*"><xsl:value-of select="."/></xsl:template>
<xsl:template match="/">
<HTML>
<HEAD>
<TITLE>Liste de patients</TITLE>
</HEAD>
<BODY>
<xsl:apply-templates select='ListePatients'/>
</BODY>
</HTML>
</xsl:template>
<xsl:template match='ListePatients'>
<TABLE>
<xsl:for-each select='Patient'>
<xsl:sort select='Nom' order='ascending' data-type='text'/>
<TR TITLE='`ihnotvy'>
<TD><xsl:value-of select='Nom'/></TD>
<TD><xsl:value-of select='NomMarital'/></TD>
<TD><xsl:value-of select='Prinom'/></TD>
</TR>
</xsl:for-each>
</TABLE>
</xsl:template>
</xsl:stylesheet>
The result :
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<TITLE>Liste de patients</TITLE>
</HEAD>
<BODY>
<TABLE>
<TR TITLE="`ihnotvy">
<TD>`ihnotvy</TD>
<TD></TD>
<TD>Jacques</TD>
</TR>
<TR TITLE="`ihnotvy">
<TD>Stick</TD>
<TD>Laiboul</TD>
<TD>Ella</TD>
</TR>
<TR TITLE="`ihnotvy">
<TD>Zeublouse</TD>
<TD></TD>
<TD>Agathe</TD>
</TR>
</TABLE>
</BODY>
</HTML>
With JAXP :
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
<TITLE>Liste de patients</TITLE>
</HEAD>
<BODY>
<TABLE>
<TR TITLE="C C)C(C.C/C4C6C9">
<TD>C C)C(C.C/C4C6C9</TD>
<TD></TD>
<TD>Jacques</TD>
</TR>
<TR TITLE="C C)C(C.C/C4C6C9">
<TD>Stick</TD>
<TD>Laiboul</TD>
<TD>Ella</TD>
</TR>
<TR TITLE="C C)C(C.C/C4C6C9">
<TD>Zeublouse</TD>
<TD></TD>
<TD>Agathe</TD>
</TR>
</TABLE>
</BODY>
</HTML>

You can also use a PrintWriter to wrap a JspWriter
since PrintWriter has a constructor that takes any
Writer instance.I'm having the same problem, I've spent a lot of time
on it but I can't get it work.
Could you post some working code that shows how you
can do it?
Thanks.
It works now, I have used the code:
result = processor.processXSL(stylesheet, xml);
PrintWriter pw = new PrintWriter(out);
result.print(pw);
I had tried this before but there was an error in other place that prevented it to work.
Thank you anyway.

Oracle XSL Processor Bug

Description
We are currently using the XMLData class (oracle.jbo.html.databeans.XmlData)
We submit an XML document having some empty XML elements. We apply an XSL Transformation but we receive a non-conform XML Document in output!!
The problem happens when one of the XML elements is empty. Oracle XSL Processor doesn't close my open tag <textarea> with a </textarea>
XSL template:
<xsl:template name="LigneAvecDetail">
<xsl:param name="value"/>
<xsl:param name="name"/>
<xsl:param name="checkboxtag"/>
<xsl:param name="detail"/>
<tr>
<td xsl:use-attribute-sets='LigneDetailStyle'>
<xsl:choose>
<xsl:when test="string-length($value) < 1">
<input type="checkbox" value="ON" onclick="compute(this)">
<xsl:attribute name="name"><xsl:value-of select="concat('C_', $name)"/></xsl:attribute>
<xsl:attribute name="id"><xsl:value-of select="$name"/></xsl:attribute>
</input>
</xsl:when>
<xsl:otherwise>
<input type="checkbox" value="ON" onclick="compute(this)">
<xsl:attribute name="name"><xsl:value-of select="concat('C_', $name)"/></xsl:attribute>
<xsl:attribute name="id"><xsl:value-of select="$name"/></xsl:attribute>
<xsl:attribute name="checked">TRUE</xsl:attribute>
</input>
</xsl:otherwise>
</xsl:choose>
<xsl:value-of select="$checkboxtag"/>
<textarea rows="2" name="S1" cols="20"><xsl:value-of select="$detail"/></textarea>
</td>
<xsl:call-template name="GroupeRadioBouton">
<xsl:with-param name="value" select="$value"/>
<xsl:with-param name="name" select="$name"/>
</xsl:call-template>
</tr>
</xsl:template>
Here my XML document:
<Results>
<DRIOQ_BilanMe_view>
<NoSommaire>1</NoSommaire>
<AutreInfo>Autre information pertinente au dossier</AutreInfo>
<IdIntervenant>1</IdIntervenant>
<PoumonsRx></PoumonsRx>
<PoumonsTdm></PoumonsTdm>
<PoumonsAutre>B</PoumonsAutre>
<PoumonsAutreDetail>Le commentaire de l'autre detail du poumon</PoumonsAutreDetail>
<OsScint></OsScint>
<OsRx>I</OsRx>
<OsRxDetail>Le commentaire du detail RX de l'os</OsRxDetail>
<OsTdm></OsTdm>
<OsTdmDetail></OsTdmDetail>
<OsAutre></OsAutre>
<OsAutreDetail></OsAutreDetail>
<FoieEnzymes>B</FoieEnzymes>
<FoieEchographie>M</FoieEchographie>
<FoieTdm>I</FoieTdm>
<FoieAutre>B</FoieAutre>
<FoieAutreDetail>Le commentaire de l'autre detail du foie</FoieAutreDetail>
</DRIOQ_BilanMe_view>
</Results>
Thanks!

This is a known bug in the HTML Output method of 2.0.2.6 which is incorrectly
outputting elements like:
<script/>
and
<textarea/>
as
<script> instead of <script></script>
and
<textarea> instead of <textarea></textarea>
This will be fixed in 2.0.2.7. The workaround
is to have some content defaulted into the <textarea> so that it's not an empty element.

XSL processor adding white space

Hi,
Is it possible to prevent the XSL processor from inserting
white space as this can affect HTML table layout & other
things.
For example.
XSL contains the following: (On one line)
<td colspan="2" bgcolor="#000066"><img
src="/images/global_spacer01.gif"/ width="1" height="1"/></td>
is converted to (Three lines)
<td colspan="2" bgcolor="#000066">
<img rc="/images/global_spacer01.gif"/ width="1" height="1">
</td>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
null

Dougall Squair (guest) wrote:
: Hi,
: Is it possible to prevent the XSL processor from inserting
: white space as this can affect HTML table layout & other
: things.
: For example.
: XSL contains the following: (On one line)
: <td colspan="2" bgcolor="#000066"><img
: src="/images/global_spacer01.gif"/ width="1" height="1"/></td>
: is converted to (Three lines)
: <td colspan="2" bgcolor="#000066">
: <img rc="/images/global_spacer01.gif"/ width="1"
height="1">
: </td>
: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
null

Oracle xsl processor

How can I configure jdeveloper to use another xsl processor rather than the oracle processor?

Remove xmlparserv2.jar, which has the XSLT clases from Classpath & add another XSLT processor to Classpath.
Also please refer to a previous post.
Run XSQL servlet with an alternate XSLT Processor

New XSL processor release 2.2.0.8 ?

When can we expect the XSL processor release (2.2.0.8 ?) with the multi-thread bug fix?
Thanks,
null

Hi,
I replaced my previous ohw jar with ohw-2.0.6.jar: the issue regarding NPEs reported in the log when using the Tree Based TOC Navigator has been fixed. Thanks.
But now my branding logo has disappeared. In the ohwconfig.xml file, I wrote:
<brandings>
<branding imageSource="/helpsets/logo.gif" />
</brandings>
When I use the previous jar, the image location is interpreted as:
http://localhost:8080/ohw/help/webapp/2.0.0.0/helpsets/logo.gif
and the logo is displayed.
When I use the new jar, the image location is interpreted as:
http://localhost:8080/ohw/help/webapp/HELP_MAIN_NT_050310/helpsets/logo.gif
and the logo doesn't show. How come?
Thanks for your help,
Pierre

Xsl processor errors/error stream?

how can I get meaningful error information during the xsl transformation process?
if the incoming xsl is malformed, then you get a null pointer exception (and that's it) from the XSLDocument constructor. some kind of a line number would be nice...
and after setting the showWarnings and errorStream properties of the processor itself, what sorts of errors would I get? that is, if the xsl sheet makes it to the processor, it's at least well formed, and I havent been able to throw any errors with well formed xsl...
anybody else doing lots of transformations?

xsl stylesheets are also xml documents
which you could parse beforehand to
check for validity. I personally found this
to be helpful during development.

Cyrillic Characters not shown in pdf file when xsl is parsed part 2:

I am using Fop to create a pdf file from an XSL file, an XML file and a ApplicationResources.properties file.
The XML file is populated by a Java class, where the information is taken from a Russian Database. This XML file is them used to populate the XSL file.
The ApplicationResources.properties file, is in windows 1251 format, as we converted it using NativeToAscii converter.
I downloaded a cyrillic ttf file, and created a metrics file, according to the Fop website. And I had Russian appearing on my PDF from the database (not ApplicationResources.properties file though). However, the information which we were retrieving from the database would not display on the jsp pages which are part of the same application.
To fix this, we changed our database driver from a ODBC-JDBC driver, to an oracle thin type 4 driver.
Since this happened, my cyrillic characters no longer appear on my PDF file.
I know that the information from the database comes back in windows 1251 format, so I tried to put the
<?xml version="1.0" encoding="windows-1251"?>
and
<?xml version="1.0" encoding="Cp1251"?>
but when I do this, I get the following error in my log file:
L2|14:14:58:433|ExecuteThread-9|PDFService.generatePDF: class com.petrotechnics.skyobma.service.SkyobmaServiceException Exception :javax.xml.transform.TransformerConfigurationException: javax.xml.transform.TransformerException: org.xml.sax.SAXParseException: The encoding "Cp1251" is not supported.
or the windows-1251 is not supported.
I do not know what to do at all, I am really struggling and was wondering if anyone had any idea about where I can go from here, or even if someone can just tell me I am fighting a loosing battle I would be happy.
Yours Truly Hopefully,
Gillian Daniel

either you configure FOP to use a SAX Parser that supports Cp1251 or you encode your XML data to UTF-8.
we flawlessly generate Greek PDF documents out of data selected from Oracle 8.1 by using UTF-8.

C++ versrion XML/XSL processor problem

Hi Folks,
I encounted the ' ' problem when I was trying to apply XSL style sheet to XML to generate html file. It seems no matter what way I ever tried, in the html, I only see the &#38 instead of getting the '&', that eventually prevents me from getting the in html to get the non-breaking space.
I looked through almost all the discussions about the question, but I only saw the java version solution. Could anyone give me some ideas about the C++ versioin solution.
The parser version I am using is 2.0.4 in Solaris and I use the XSLSample which compiled from XSLSample.cpp.
Any help will be greatly appriciated.
Sean

Starting with version 2.0.6, you can use the disable-output-escaping attribute.
null

XSL Processor

Hi,
I am currently using XDK for my project. I need to know how do i use the XSLT processor in XDK?. i have no idea and i have been looking on the oracle site to find a how to document.
Will i need to download anything? or is it already there?.
Thanks
Jagdish

Hi,
How do i install these files? Is there a document that you could point me towards. I have found ncomp_xmlparserv2. jar files. There are two, are these the files that you are refering to? I am looking for the XML parser and also the XSLT processor.
Thanks

Cyrillic Characters not shown in pdf file when xsl is parsed

Part of the application we have created allows the user to view PDF pages, so they are more suitable for printing.
We create xsl files which eventually get transformed into the PDF format.
We use the javax.xml.Transform.Transformer to transform the xsl file and xml.
We use the org.exolab.castor.xml.Marshallerto general the xml.
We use Apache Fop to turn the XML into the PDF format.
Before it was working fine, we get some text from a resource file, which we call in the xsl. But now we want to do this in Russian. When we read the same resource file in the xsl, but with the cyrillic characters in it, the pdf view is just question marks, and other characters. Nothing russian.
Does anyone know where I could start looking to find out what is wrong?

just generate the font metrics files for the fonts you intend to use, as explained on FOP web site, then you will get the Cyrillic chars.

Using multiple XSL files parsing a XML file

Hi,
Can a single XML be procesed by a XSL file in which are included many XSL stylesheet?
I mean, my Java servlet writes the results of the SQL
queries in a single XML document. Something like this:
<?xml version="1.0" encoding="UTF-8" ?>
<body>

<record>
<nombre>Monica</nombre>
<apellido1>Amann</apellido1>
<apellido2>Ostos</apellido2>
</record>

<record>
<domicilio>Rodriguez Arias</domicilio>
<numero>41</numero>
<piso>5</piso>
</record>

<record>
<nombre>Ana</nombre>
<apellido1>Garcia</apellido1>
<apellido2>Ostos</apellido2>
<domicilio>Rodriguez Arias</domicilio>
<numero>41</numero>
<piso>5</piso>
<mano>Decha</mano>
</record>
</body>
I want to be able to apply a particular stylesheet into diferent part of the XML file.
I mean, i have a XSL (father), in which are included various XSL. My problem is that
i can apply the bloque1.xsl to process part1 in the xml, and bloque2.xsl to process
part2 in the xml and the same with the thrid.
This is my XSL (father), but i don't know whats the way to do it. And i don�t konw if
it's possible to do it.
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsl:stylesheet
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:fo="http://www.w3.org/1999/XSL/Format"
version="1.0">
<xsl:include href="/aplic/fop/ejemplos/bloque1.xsl" />
<xsl:include href="/aplic/fop/ejemplos/bloque2.xsl" />
<xsl:include href="/aplic/fop/ejemplos/bloque3.xsl" />
<xsl:template match="body">
     <fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format">
          <fo:layout-master-set>
          <fo:simple-page-master master-name="simple"
               page-height="21cm"
               page-width="21cm"
               margin-top="1cm"
               margin-bottom="1cm"
               margin-left="1.5cm"
               margin-right="1.5cm">
               <fo:region-body margin-top="1.5cm"
               margin-bottom="1.5cm"/>
          </fo:simple-page-master>
          </fo:layout-master-set>
          <fo:page-sequence master-reference="simple">
          <fo:flow flow-name="xsl-region-body">
          <fo:block text-align="right">
                    <fo:external-graphic src="c:\aplic\fop\ejemplos\barcode.jpeg" width="8.1cm" height="3.7cm"/>
          </fo:block>
               <xsl:apply-templates/>
          </fo:flow>
          </fo:page-sequence>
     </fo:root>
</xsl:template>

</xsl:stylesheet>
Finally i have to produce a single resultant report into pdf outformat. For this, i am using XSL-FO.
Thanks a lot, and i'm sorry for my english language.

The examples of Xalan (check xml.apache.org) do just that.
Micks

XSL Processor Parser C++

Similar Messages

Maybe you are looking for