Oracle XML processor is not handling variable properly

I use the XML Parser 2.0.2.7 to process an XML transformation but I don't get the expected result. Running this example with other XML Processor get the job done (IBM, Excelon, Microsoft). I read again the normative document on www.w3c.org on XSL and I believe that your processor fail to render my XSL transformation because it doesn't handle variable properly.
So, here is my XML document and my XSL stylesheet:
XML Document:
<Results>
<Usager>
<IdUsager>34</IdUsager>
<NomUsager>NomUsager</NomUsager>
<PrenomUsager>Le prenom de l'usager</PrenomUsager>
<NoAssuranceMaladie>ZZZZ12121212</NoAssuranceMaladie>
<dossiersommaire_view>
<UsagerSommaire>
<IdEven>2</IdEven>
<TypeElement>16</TypeElement>
<IdUsager>34</IdUsager>
<IdUtilisateur>1</IdUtilisateur>
<DateDebut>1998-04-05</DateDebut>
<IdDoc>5</IdDoc>
<IdCatgElement>6</IdCatgElement>
<Description>Initial</Description>
<IdTypeElement>16</IdTypeElement>
<IdCatgElement1>6</IdCatgElement1>
<Description1>Bilan mitastatique initial</Description1>
<IdUtilisateur1>1</IdUtilisateur1>
<CodeProfil>3</CodeProfil>
<CodeProfil1>3</CodeProfil1>
<TypeElement1>16</TypeElement1>
<DroitAcces>M</DroitAcces>
</UsagerSommaire>
<UsagerSommaire>
<IdEven>30</IdEven>
<TypeElement>15</TypeElement>
<IdUsager>34</IdUsager>
<IdUtilisateur>1</IdUtilisateur>
<DateDebut>2000-06-08</DateDebut>
<IdDoc>31</IdDoc>
<IdCatgElement>6</IdCatgElement>
<Description>Initial</Description>
<IdTypeElement>15</IdTypeElement>
<IdCatgElement1>6</IdCatgElement1>
<Description1>Sommaire initial</Description1>
<IdUtilisateur1>1</IdUtilisateur1>
<CodeProfil>3</CodeProfil>
<CodeProfil1>3</CodeProfil1>
<TypeElement1>15</TypeElement1>
<DroitAcces>M</DroitAcces>
</UsagerSommaire>
<UsagerSommaire>
<IdEven>7</IdEven>
<TypeElement>6</TypeElement>
<IdUsager>34</IdUsager>
<IdUtilisateur>1</IdUtilisateur>
<DateDebut>2000-04-15</DateDebut>
<IdDoc>1</IdDoc>
<IdCatgElement>2</IdCatgElement>
<Description>Examens</Description>
<IdTypeElement>6</IdTypeElement>
<IdCatgElement1>2</IdCatgElement1>
<Description1>Examens numirisis</Description1>
<IdUtilisateur1>1</IdUtilisateur1>
<CodeProfil>3</CodeProfil>
<CodeProfil1>3</CodeProfil1>
<TypeElement1>6</TypeElement1>
<DroitAcces>C</DroitAcces>
</UsagerSommaire>
<UsagerSommaire>
<IdEven>9</IdEven>
<TypeElement>2</TypeElement>
<IdUsager>34</IdUsager>
<IdUtilisateur>1</IdUtilisateur>
<DateDebut>2000-03-14</DateDebut>
<IdDoc>1</IdDoc>
<IdCatgElement>1</IdCatgElement>
<Description>Suivi</Description>
<IdTypeElement>2</IdTypeElement>
<IdCatgElement1>1</IdCatgElement1>
<Description1>Suivi oncologique</Description1>
<IdUtilisateur1>1</IdUtilisateur1>
<CodeProfil>3</CodeProfil>
<CodeProfil1>3</CodeProfil1>
<TypeElement1>2</TypeElement1>
<DroitAcces>C</DroitAcces>
</UsagerSommaire>
<UsagerSommaire>
<IdEven>10</IdEven>
<TypeElement>2</TypeElement>
<IdUsager>34</IdUsager>
<IdUtilisateur>1</IdUtilisateur>
<DateDebut>2000-03-27</DateDebut>
<IdDoc>1</Id Doc>
<IdCatgElement>1</IdCatgElement>
<Description>Suivi</Description>
<IdTypeElement>2</IdTypeElement>
<IdCatgElement1>1</IdCatgElement1>
<Description1>Suivi oncologique</Description1>
<IdUtilisateur1>1</IdUtilisateur1>
<CodeProfil>3</CodeProfil>
<CodeProfil1>3</CodeProfil1>
<TypeElement1>2</TypeElement1>
<DroitAcces>C</DroitAcces>
</UsagerSommaire>
<UsagerSommaire>
<IdEven>16</IdEven>
<TypeElement>16</TypeElement>
<IdUsager>34</IdUsager>
<IdUtilisateur>1</IdUtilisateur>
<DateDebut>2000-06-05</DateDebut>
<IdDoc>46</IdDoc>
<IdCatgElement>6</IdCatgElement>
<Description>Initial</Description>
<IdTypeElement>16</IdTypeElement>
<IdCatgElement1>6</IdCatgElement1>
<Description1>Bilan mitastatique initial</Description1>
<IdUtilisateur1>1</IdUtilisateur1>
<CodeProfil>3</CodeProfil>
<CodeProfil1>3</CodeProfil1>
<TypeElement1>16</TypeElement1>
<DroitAcces>M</DroitAcces>
</UsagerSommaire>
<UsagerSommaire>
<IdEven>26</IdEven>
<TypeElement>15</TypeElement>
<IdUsager>34</IdUsager>
<IdUtilisateur>1</IdUtilisateur>
<DateDebut>2000-06-07</DateDebut>
<IdDoc>32</IdDoc>
<IdCatgElement>6</IdCatgElement>
<Description>Initial</Description>
<IdTypeElement>15</IdTypeElement>
<IdCatgElement1>6</IdCatgElement1>
<Description1>Sommaire initial</Description1>
<IdUtilisateur1>1</IdUtilisateur1>
<CodeProfil>3</CodeProfil>
<CodeProfil1>3</CodeProfil1>
<TypeElement1>15</TypeElement1>
<DroitAcces>M</DroitAcces>
</UsagerSommaire>
<UsagerSommaire>
<IdEven>37</IdEven>
<TypeElement>15</TypeElement>
<IdUsager>34</IdUsager>
<IdUtilisateur>1</IdUtilisateur>
<DateDebut>2000-06-08</DateDebut>
<IdDoc>32</IdDoc>
<IdCatgElement>6</IdCatgElement>
<Description>Initial</Description>
<IdTypeElement>15</IdTypeElement>
<IdCatgElement1>6</IdCatgElement1>
<Description1>Sommaire initial</Description1>
<IdUtilisateur1>1</IdUtilisateur1>
<CodeProfil>3</CodeProfil>
<CodeProfil1>3</CodeProfil1>
<TypeElement1>15</TypeElement1>
<DroitAcces>M</DroitAcces>
</UsagerSommaire>
</dossiersommaire_view>
<categorie_view>
<CatgElement>
<IdCatgElement>1</IdCatgElement>
<Description>Suivi</Description>
<type_view>
<TypeElement>
<IdTypeElement>2</IdTypeElement>
<IdCatgElement>1</IdCatgElement>
<Description>Suivi oncologique</Description>
<CodeProfil>3</CodeProfil>
<TypeElement>2</TypeElement>
<DroitAcces>C</DroitAcces>
<IdUtilisateur>1</IdUtilisateur>
<CodeProfil1>3</CodeProfil1>
</TypeElement>
<TypeElement>
<IdTypeElement>5</IdTypeElement>
<IdCatgElement>1</IdCatgElement>
<Description>Suivi pharmaceutique</Description>
<CodeProfil>3</CodeProfil>
<TypeElement>5</TypeElement>
<DroitAcces>M</DroitAcces>
<IdUtilisateur>1</IdUtilisateur>
<CodeProfil1>3</CodeProfil1>
</TypeElement>
<TypeElement>
<IdTypeElement>3</IdTypeElement>
<IdCatgElement>1</IdCatgElement>
<Description>Suivi avec chimiothirapie</Description>
<CodeProfil>3</CodeProfil>
<TypeElement>3</TypeEleme nt>
<DroitAcces>M</DroitAcces>
<IdUtilisateur>1</IdUtilisateur>
<CodeProfil1>3</CodeProfil1>
</TypeElement>
<TypeElement>
<IdTypeElement>4</IdTypeElement>
<IdCatgElement>1</IdCatgElement>
<Description>Evaluation psychosociale</Description>
<CodeProfil>3</CodeProfil>
<TypeElement>4</TypeElement>
<DroitAcces>M</DroitAcces>
<IdUtilisateur>1</IdUtilisateur>
<CodeProfil1>3</CodeProfil1>
</TypeElement>
</type_view>
</CatgElement>
<CatgElement>
<IdCatgElement>2</IdCatgElement>
<Description>Examens</Description>
<type_view>
<TypeElement>
<IdTypeElement>6</IdTypeElement>
<IdCatgElement>2</IdCatgElement>
<Description>Examens numirisis</Description>
<CodeProfil>3</CodeProfil>
<TypeElement>6</TypeElement>
<DroitAcces>C</DroitAcces>
<IdUtilisateur>1</IdUtilisateur>
<CodeProfil1>3</CodeProfil1>
</TypeElement>
</type_view>
</CatgElement>
<CatgElement>
<IdCatgElement>3</IdCatgElement>
<Description>Ricidive</Description>
<type_view>
<TypeElement>
<IdTypeElement>7</IdTypeElement>
<IdCatgElement>3</IdCatgElement>
<Description>Ricidives</Description>
<CodeProfil>3</CodeProfil>
<TypeElement>7</TypeElement>
<DroitAcces>C</DroitAcces>
<IdUtilisateur>1</IdUtilisateur>
<CodeProfil1>3</CodeProfil1>
</TypeElement>
</type_view>
</CatgElement>
<CatgElement>
<IdCatgElement>4</IdCatgElement>
<Description>Mitastase</Description>
<type_view>
<TypeElement>
<IdTypeElement>8</IdTypeElement>
<IdCatgElement>4</IdCatgElement>
<Description>Mitastases</Description>
<CodeProfil>3</CodeProfil>
<TypeElement>8</TypeElement>
<DroitAcces>M</DroitAcces>
<IdUtilisateur>1</IdUtilisateur>
<CodeProfil1>3</CodeProfil1>
</TypeElement>
</type_view>
</CatgElement>
<CatgElement>
<IdCatgElement>5</IdCatgElement>
<Description>Traitement</Description>
<type_view>
<TypeElement>
<IdTypeElement>9</IdTypeElement>
<IdCatgElement>5</IdCatgElement>
<Description>Chimiothirapie (nursing onco)</Description>
<CodeProfil>3</CodeProfil>
<TypeElement>9</TypeElement>
<DroitAcces>M</DroitAcces>
<IdUtilisateur>1</IdUtilisateur>
<CodeProfil1>3</CodeProfil1>
</TypeElement>
<TypeElement>
<IdTypeElement>10</IdTypeElement>
<IdCatgElement>5</IdCatgElement>
<Description>Hormonothirapie (nursing onco)</Description>
<CodeProfil>3</CodeProfil>
<TypeElement>10</TypeElement>
<DroitAcces>C</DroitAcces>
<IdUtilisateur>1</IdUtilisateur>
<CodeProfil1>3</CodeProfil1>
</TypeElement>
<TypeElement>
<IdTypeElement>12</IdTypeElement>
<IdCatgElement>5</IdCatgElement>
<Description>Radiothirapie - plan de traitement</Description>
<CodeProfil>3</CodeProfil>
<TypeElement>12</TypeElement>
<DroitAcces>C</DroitAcces>
<IdUtilisateur>1</IdUtilisateur>
<CodeProfil1>3</CodeProfil1>
</TypeElement>
<TypeElement>
<IdTypeElement>13</IdTypeElement>
<IdCatgElement>5</IdCatgElement>
<Description>Radiothirapie - note de fin de traitement (rapport numirisi)</Description>
<CodeProfil>3</CodeProfil>
<TypeElement&gt ;13</TypeElement>
<DroitAcces>C</DroitAcces>
<IdUtilisateur>1</IdUtilisateur>
<CodeProfil1>3</CodeProfil1>
</TypeElement>
<TypeElement>
<IdTypeElement>14</IdTypeElement>
<IdCatgElement>5</IdCatgElement>
<Description>Chirurgie (rapport numirisi)</Description>
<CodeProfil>3</CodeProfil>
<TypeElement>14</TypeElement>
<DroitAcces>M</DroitAcces>
<IdUtilisateur>1</IdUtilisateur>
<CodeProfil1>3</CodeProfil1>
</TypeElement>
</type_view>
</CatgElement>
<CatgElement>
<IdCatgElement>6</IdCatgElement>
<Description>Initial</Description>
<type_view>
<TypeElement>
<IdTypeElement>15</IdTypeElement>
<IdCatgElement>6</IdCatgElement>
<Description>Sommaire initial</Description>
<CodeProfil>3</CodeProfil>
<TypeElement>15</TypeElement>
<DroitAcces>M</DroitAcces>
<IdUtilisateur>1</IdUtilisateur>
<CodeProfil1>3</CodeProfil1>
</TypeElement>
<TypeElement>
<IdTypeElement>16</IdTypeElement>
<IdCatgElement>6</IdCatgElement>
<Description>Bilan mitastatique initial</Description>
<CodeProfil>3</CodeProfil>
<TypeElement>16</TypeElement>
<DroitAcces>M</DroitAcces>
<IdUtilisateur>1</IdUtilisateur>
<CodeProfil1>3</CodeProfil1>
</TypeElement>
</type_view>
</CatgElement>
<CatgElement>
<IdCatgElement>7</IdCatgElement>
<Description>Autre</Description>
<type_view>
<TypeElement>
<IdTypeElement>17</IdTypeElement>
<IdCatgElement>7</IdCatgElement>
<Description>Note du midecin</Description>
<CodeProfil>3</CodeProfil>
<TypeElement>17</TypeElement>
<DroitAcces>C</DroitAcces>
<IdUtilisateur>1</IdUtilisateur>
<CodeProfil1>3</CodeProfil1>
</TypeElement>
</type_view>
</CatgElement>
</categorie_view>
</Usager>
</Results>
XSL Stylesheet:
<?xml version="1.0" encoding='ISO-8859-1'?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
<xsl:output indent="yes" method="text" 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="/"><xsl:text><html>
</xsl:text>
<xsl:text><BODY BGCOLOR= "#CEDFC6">
</xsl:text>
<xsl:text><APPLET CODEBASE="/applets/" CODE="SIRtree.class" WIDTH=200 HEIGHT=380>
</xsl:text>
<xsl:text><PARAM NAME="TITLEFONT" VALUE="0">
</xsl:text>
<xsl:text><PARAM NAME="ICONS" VALUE="/applets/DRQICON.gif">
</xsl:text>
<xsl:text><PARAM NAME="BGCOLOR" VALUE="8">
</xsl:text>
<xsl:text><PARAM NAME="NODEFONT" VALUE="3">
</xsl:text>
<xsl:text><PARAM NAME="HBGCOLOR" VALUE="2">
</xsl:text>
<xsl:text><PARAM NAME="TXTCOLOR" VALUE="2">
</xsl:text>
<xsl:text><PARAM NAME="HTXTCOLOR" VALUE="10">
</xsl:text>
<xsl:text><PARAM NAME="FONT1" VALUE="Helvetica|B">
</xsl:text>
<xsl:text><PARAM NAME="FONT2" VALUE="Helvetica|N">
</xsl:text>
<xsl:text><PARAM NAME="FONT3" VALUE="Arial|N">
</xsl:text>
<xsl:text>
</xsl:text>
<xsl:text><PARAM NAME="Color1" VALUE="150|150|150">
</xsl:text>
<xsl:text>
</xsl:text>
<xsl:text><PARAM NAME="Color2" VALUE="0|0|0">
</xsl:text>
<xsl:te xt>
</xsl:text>
<xsl:text><PARAM NAME="Color3" VALUE="0|0|255">
</xsl:text>
<xsl:text>
</xsl:text>
<xsl:text><PARAM NAME="Color4" VALUE="255|0|0">
</xsl:text>
<xsl:text>
</xsl:text>
<xsl:text><PARAM NAME="Color5" VALUE="255|128|0">
</xsl:text>
<xsl:text>
</xsl:text>
<xsl:text><PARAM NAME="Color6" VALUE="100|100|100">
</xsl:text>
<xsl:text>
</xsl:text>
<xsl:text><PARAM NAME="Color7" VALUE="200|200|200">
</xsl:text>
<xsl:text>
</xsl:text>
<xsl:text><PARAM NAME="Color8" VALUE="206|223|198">
</xsl:text>
<xsl:text>
</xsl:text>
<xsl:text><PARAM NAME="Color9" VALUE="255|255|0">
</xsl:text>
<xsl:text>
</xsl:text>
<xsl:text><PARAM NAME="Color10" VALUE="255|255|255">
</xsl:text>
<xsl:text><PARAM NAME="BORDER" VALUE="0">
</xsl:text>
<xsl:text>
</xsl:text>
<xsl:variable name="NodeCPT" select='3'/>
<xsl:text><PARAM NAME="NODE0" VALUE="ROOT|</xsl:text><xsl:value-of select="Results/Usager/NomUsager"/><xsl:text>"|1| | | | |0|-1">
</xsl:text>
<xsl:text><PARAM NAME="NODE1" VALUE="ROOT|</xsl:text><xsl:value-of select="Results/Usager/PrenomUsager"/><xsl:text>"|1| | | | |0|-1">
</xsl:text>
<xsl:text><PARAM NAME="NODE2" VALUE="ROOT|</xsl:text><xsl:value-of select="Results/Usager/NoAssuranceMaladie"/><xsl:text>"|1| | | | |0|-1">
</xsl:text>
<xsl:for-each select="/Results/Usager/categorie_view/CatgElement">
<xsl:variable name="Racine" select="Description"/>
<xsl:text><PARAM NAME="NODE</xsl:text><xsl:value-of select="$NodeCPT"/><xsl:text>" VALUE="ROOT|</xsl:text><xsl:value-of select="$Racine"/><xsl:text>|1| |mainFrame| | |1|-1|4">
</xsl:text>
<xsl:variable name="NodeCPT" select="$NodeCPT+1"/>
<xsl:text>
// Ajouter les Types d'iliment
</xsl:text>
<xsl:for-each select="type_view/TypeElement">
<xsl:variable name="Feuille" select="Description"/>
<xsl:text><PARAM NAME="NODE</xsl:text><xsl:value-of select="$NodeCPT"/><xsl:text>" VALUE="</xsl:text><xsl:value-of select="$Racine"/><xsl:text>|</xsl:text><xsl:value-of select="Description"/><xsl:text>|1| |mainFrame| | |1|-1|4">
</xsl:text>
<xsl:variable name="NodeCPT" select="$NodeCPT+1"/>
<xsl:variable name="DroitAcces" select="DroitAcces"/>
<xsl:if test="$DroitAcces = 'M'">
<xsl:text><PARAM NAME="NODE</xsl:text><xsl:value-of select="$NodeCPT"/><xsl:text>" VALUE="</xsl:text><xsl:value-of select="$Feuille"/><xsl:text>|Ajouter...|3|http://drioq.qc.cgi.ca/jspdrioq/Elem_Query.jsp?IdTypeElem=</xsl:text><xsl:value-of select="TypeElementId"/><xsl:text>|mainFrame| | |0">
</xsl:text>
<xsl:variable name="NodeCPT" select="$NodeCPT+1"/>
</xsl:if>
<xsl:variable name="TypeElement" select="IdTypeElement"/>
<xsl:for-each select="//Results/Usager/dossiersommaire_view/UsagerSommaire[TypeElement=$TypeElement]">
<xsl:text><PARAM NAME="NODE</xsl:text><xsl:value-of select="$NodeCPT"/><xsl:text>" VALUE="</xsl:text><xsl:value-of select="$Feuille"/><xsl:text>|</xsl:text><xsl:value-of select="Description"/><xsl:text> du </xsl:text><xsl:value-of select="DateDebut"/><xsl:text>|2|http://drioq.qc.cgi.ca/jspdrioq/Elem_Query.jsp?IdEven=</xsl:text><xsl:value-of select="I dEven"/><xsl:text>|mainFrame| | |0">
</xsl:text>
<xsl:variable name="NodeCPT" select="$NodeCPT+1"/>
</xsl:for-each>
<xsl:if test="($DroitAcces = 'C')">
<xsl:if test="(count(//Results/Usager/dossiersommaire_view/UsagerSommaire[TypeElement=$TypeElement]) = 0)">
<xsl:text><PARAM NAME="NODE</xsl:text><xsl:value-of select="$NodeCPT"/><xsl:text>" VALUE="</xsl:text><xsl:value-of select="$Feuille"/><xsl:text>|Aucun Dossier |5| | | | |0">
</xsl:text>
<xsl:variable name="NodeCPT" select="$NodeCPT+1"/>
</xsl:if>
</xsl:if>
</xsl:for-each>
</xsl:for-each>
<xsl:text>
//-----------------------------------PAS TOUCHE----------------------------------------------------------
</xsl:text>
<xsl:text></BODY>
</xsl:text>
<xsl:text></html>
</xsl:text>
</xsl:template>
</xsl:stylesheet>
null

First of all, thank for Steve and Micheal for your help.
Well, it's that I don't read section 11.5 before I posted my last messages(I don't know how I did that??? may be to much nightly development) Also I think that xsl:variable just lead to misunderstanding. I would prefere the "xsl:constant" label.
In neither way, I'm still looking for a solution to number my parameter because I don't each time how many parameter I'll have to pass to my applets. I'm now looking for pure JSP.
Steve you also pointed out that the use of <xsl:text> is very strange! You're right! The main reason why I'm working that way is because we need to generate JavaScript based on the XML Data. So I start my stylesheet in text mode because I need to generate text (JavaScript) and not only tag like "PARAM". But to simply this example and focus on the problem I retired the JavaScript Part and any other not relevent tag! If there is a way to change the output mode after generating the JavaScript I would like to know about it.
Ok, everyone thanks again!

Similar Messages

Error while loadjava xmlparserv2.jar: ORA-04043: object oracle/xml/.. does not exist

In Oracle8i.15, I tried to install xmlparserv2.jar after I downloaded xdk_plsql_9_2_0_2_0.zip and upzip to local machine.
However, when I issued the follwoing command:
loadjava -v -r -user SYSTEM/manager -force xmlparserv2.jar
For each class, it has the following error message:
resolving: oracle/xml/async/DOMBuilderErrorListener
Error while resolving class oracle/xml/async/DOMBuilderErrorListener
ORA-04043: object oracle/xml/async/DOMBuilderErrorListener does not exist
resolving: oracle/xml/comp/CXMLParser
Error while resolving class oracle/xml/comp/CXMLParser
ORA-04043: object oracle/xml/comp/CXMLParser does not exist
How can I solve this problem?
Thanks in advance.

Do you mean you use 8.1.5? You can't directly load the xmlparserv2.jar to it.

Why Oracle XML parser do not compile this file and Apache does?

Hi:
I am trying to parse this xml file:
http://cvs.apache.org/viewcvs.cgi/xml-cocoon2/documentation/xdocs/userdocs/xsp/logicsheet-concepts.xml?rev=1.2&content-type=text/vnd.viewcvs-markup
and fails with the tag <anchor id="logicsheet"/>, if I change
"logicsheet" to "id_lg" it works fine.
Apache XML parsers do not have this problem.
Best regards, Marcelo.

I tried downloading the file and (after removing the DOCTYPE
since I didn't want to download the whole set of DTD's) it
parses fine with XDK 9.0.2C
Which XDK are you using?
If you remove the <!DOCTYPE> line for a test, does it still fail?

BUG: Oracle Schema Processor does not work in Servlets

We found a bug with Oracle's Schema Processor. It does not work in Servlets.
When we try to validate a XML document in a Servlet it does not work, but we can execute the same code in a stand alone application and it works.
The following is the code we are using:
try {
File f =new File(filename);
FileReader r = new FileReader(f);
DOMParser dp = new DOMParser();
URL url = createURL (filename);
dp.setValidationMode(false);
dp.setSchemaValidationMode(true);
dp.setPreserveWhitespace(true);
dp.parse(url);
System.out.println("it is parsed");
} catch(Exception e){System.out.println("there is Error"+e.getMessage());}
null

I don't think this is related to Servlets per se.
Check that the Schema processor classes used by the servlet container, and your application are the same.
Java does not have proper versioning of classes, I have seen many applications collapse. People compiled their code on developer machines, where it worked fine, but when moved to a production machine they failed because the production machine had a different version of classes. Usually the name of the class doesn't change, but either a method or a variable is missing in several classes. VM doesn't complain but simply crashes.
In your Schema Processor classes that are used by the servlet engine might be different from the one that the app uses. Do a search on the file system to see how many copy of the same class bundle (zip, jar) you have on the system.

Recorded ACTIONS not handling typography properly in PS6 beta

Recorded Actions are not properly rendering the scaling and placement of fonts when played back.
1) Go to http://www.psdcovers.com
2) Download any Action
3) Install and run "STEP 1 ••• Prepare Template"
The issue should be obvious and staring at you in the face when using PS6 beta. The fonts are not scaled and positioned as recorded in the Actions which work fine all the way back to CS3.
Sincerely,
Simon

Here is what they are talking about:
Action results from CS5:
Action results from CS6:
I also notice that the action is much slower in CS6.
But the thing is that loading actions created in previous versions of Photoshop into newer ones, you can't aways expect things to work exactly the same way. There is always the chance for something like this to happen. Especially with the changes to text handling in CS6. I did notice that the text is two different sizes once created between CS5 and CS6. I'm trying to pick apart the action to see what is going on...

Oracle JDBC driver does not handle Java empty strings correctly

If you store a Java empty string in a VARCHAR column, then try to retrieve it,
you get back a null.
Can someone from Oracle JDBC development
explain why this is not a bug? An empty
string is not the same as a null.

Hello!
Although all together different, but DATE type also behaves same way.
inserting createdate = NULL in database returns you blank on select query
inserting createdate= '' returns null on select. Correct me if i am wrong.
prity
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Nagaraj Govindaraj ([email protected]):
If you store a Java empty string in a VARCHAR column, then try to retrieve it,
you get back a null.
Can someone from Oracle JDBC development
explain why this is not a bug? An empty
string is not the same as a null.<HR></BLOCKQUOTE>
null

Howto force Oracle XML parser not to expand entity references?

Hi,
Is it possible to force Oracle XML parser (Java) not to expand entity references, so that they appear in DOM tree as separated nodes after parsing XML?
Example:
for following XML
<tag>abcäxyz</tag>
I get:
Element: "tag"
|-Text: "abcdxyz"
but I would like to get:
Element: "tag"
|-Text: "abc"
|
|-EntityReference: "auml"
|
|-Text: "xyz"
I've already tried to use JAXP api (setExpandEntityReferences method in java.xml.parsers.DocumentBuilderFactory), but it doesn't seem to work.
I'm using parser from XDK Java v9.2.0.2.0 Production.
Thx,
James

This is requested code sample:
DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
dbf.setExpandEntityReferences(false);
System.out.println("isExpandEntityReferences = "+dbf.isExpandEntityReferences());
DocumentBuilder db = dbf.newDocumentBuilder();
Document d = db.parse("file://c:/test.xml");
Element e = d.getDocumentElement();
System.out.println("documentElement"+ e.getTagName() + " nodeType=" +e.getNodeType());
System.out.println("ChildNodes:");
NodeList nodeList = e.getChildNodes();
for(int i=0; i<nodeList.getLength();i++) {
System.out.println(i+" value=\""+nodeList.item(i).getNodeValue()+"\" nodeType="+nodeList.item(i).getNodeType());
Content of test.xml:
<!DOCTYPE test SYSTEM "test.dtd">
<test>abcäxyz</test>
Content of test.dtd:
<!ELEMENT test (#PCDATA)>
<!ENTITY auml "ä">
When you run it you will get the following output:
isExpandEntityReferences = true
documentElementtest nodeType=1
ChildNodes:
0 value="abcdxyz" nodeType=3
which means that EntityReference has been expanded.
As you can see in the output the isExpandEntityReferences method returns "true", even though I set it to false in code!
Does it mean that Oracle parser simple doesn't support this feature???
Thx,
James

Weaknesses I've come across in the Oracle XML/XSL implementation

Weaknesses I've come across in the Oracle XML/XSL implementation
NOTE: I think Oracle is a fantastic database and the XML implementation is lovely to use - also I know these are not limited to XE and also that some are fixed in 11g enterprise however I'm not sure if all are so I am posting here in the hope that Oracle will include fixes for all if any have been missed
1. getclobval() returns a spurious carriage return on end of the value returned
2. extract does not handle mixed content tags well (for example it simply discards tags that only have whitespace between them
3. XSL: using a xsl:number level="multiple" with anything beyond a simple count= xpath value crashes the database completely
4. XSL: insists on pretty printing output XML which is extremely odd behaviour and causes problems when dealing with mixed content

Another weakness I've seen is with the appendchildxml function and mixed content xml - it appears to likewise pretty print XML causing the injection of carriage returns and whitespace into mixed content nodes

Fatal Error and NullPointerException in Oracle XML Transformer

Hi,
I'm building a dom tree in memory with oracle xml parser. Then I transform the dom document into a string to send xml to the client. But I get an fatal error on calling transform.
I don't know what could be the problem, because apache and weblogic parser works, an when I create a dom document with org.w3c.dom elements and statements then the xml document can't be invalid,
because the document implementation would throw an exception if wrong nodes or something like this should be inserted...
I'm using oracle xml parser 9.2.0.4 for java, bea weblogic 7.0 and win2k.
Thanks for help.
XSL-1900: (Fatal Error) An internal error condition occurred.
javax.xml.transform.TransformerException: XSL-1900: (Fatal Error) An internal error condition occurred.
at oracle.xml.jaxp.JXTransformer.reportException(JXTransformer.java:681)
at oracle.xml.jaxp.JXTransformer.transform(JXTransformer.java:309)
java.lang.NullPointerException
at oracle.xml.parser.v2.XSLSAXPrintDriver.printAttributes(XSLSAXPrintDriver.java:394)
at oracle.xml.parser.v2.XSLSAXPrintDriver.startElement(XSLSAXPrintDriver.java:322)
at oracle.xml.parser.v2.XMLElement.reportSAXEvents(XMLElement.java:993)
at oracle.xml.parser.v2.XMLNode.reportChildSAXEvents(XMLNode.java:1014)
at oracle.xml.parser.v2.XMLDocument.reportSAXEvents(XMLDocument.java:942)
at oracle.xml.jaxp.JXTransformer.transform(JXTransformer.java:294)

Hi,
I'm having that problem to:
I'm getting the following exception
javax.xml.transform.TransformerException: XSL-1900: (Fatal Error) An internal error condition occurred.
     at oracle.xml.jaxp.JXTransformer.reportException(JXTransformer.java:723)
     at oracle.xml.jaxp.JXTransformer.transform(JXTransformer.java:340)
     at com.ac.mqif.control.Handler.handleLong(Handler.java:835)
     at com.ac.mqif.control.Handler.run(Handler.java:951)
Caused by: java.lang.NullPointerException
     at oracle.xml.parser.v2.XPathStep.getSelectedNodes(XPathStep.java:380)
     at oracle.xml.parser.v2.PathExpr.getValue(XSLNodeSetExpr.java:483)
     at oracle.xml.parser.v2.XSLExprBase.getStringValue(XSLExprBase.java:363)
     at oracle.xml.parser.v2.XSLValueOf.processAction(XSLValueOf.java:99)
     at oracle.xml.parser.v2.XSLNode.processChildren(XSLNode.java:367)
     at oracle.xml.parser.v2.XSLTemplate.processAction(XSLTemplate.java:199)
     at oracle.xml.parser.v2.XSLApplyTemplates.processAction(XSLApplyTemplates.java:214)
     at oracle.xml.parser.v2.XSLApplyTemplates.processAction(XSLApplyTemplates.java:207)
     at oracle.xml.parser.v2.XSLApplyTemplates.processAction(XSLApplyTemplates.java:207)
     at oracle.xml.parser.v2.XSLApplyTemplates.processAction(XSLApplyTemplates.java:120)
     at oracle.xml.parser.v2.XSLNode.processChildren(XSLNode.java:367)
     at oracle.xml.parser.v2.XSLTemplate.processAction(XSLTemplate.java:199)
     at oracle.xml.parser.v2.XSLStylesheet.execute(XSLStylesheet.java:471)
     at oracle.xml.parser.v2.XSLStylesheet.execute(XSLStylesheet.java:448)
     at oracle.xml.parser.v2.XSLProcessor.processXSL(XSLProcessor.java:246)
     at oracle.xml.jaxp.JXTransformer.transform(JXTransformer.java:327)
     ... 2 more
when using a stylesheet which has a template match condition of more than 1600 characters.
The second thing is that the Oracle XML transformer is
NOT threadsafe. I was using several threads using different templates to transform an incoming XML simultaneously but was ALWAYS getting internal XSL errors
and Nullpointer Exceptions. I solved this by synchronizing the transformation, but I don't like it.
I'm using the following versions on Windows XP:
Oracle IDE: 9.0.3.10.35
Business Components Version: 9.0.3.10.7
SCM Support Version: 9.0.3.9.4
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-b28)
Thanx,
Ellcrys

Error in oracle.xml.sql.query

I am trying to write small piece of code as
follows
import java.sql.*;
import java.math.*;
import oracle.xml.sql.query.*;
import oracle.jdbc.*;
import oracle.jdbc.driver.*;
Actual Code
When i try to compile
the java file it errors out on Package Oracle.xml.sql.query not found in import
Pacakage oracle.jdbc.* not found
Package oracle.jdbc.driver not found
Is there any files to be installed.
I installed default Enterprise edition of Oracle 8.1.7 on NT
Please advise
Thanks,
Vidhya
null

Have you include classes12.jar/zip, xsu12.jar in your classpath?(assume using JDK 1.2.x)

Setting up Oracle XML Gateway for EBS 12.1.3

Hi Experts,
We are currently working on R12.1.3 and was asked to check on how to setup/integrate XML Gateway on R12.1.3.
I have gone though many pages of this forums and checked the support ID's as given below :
Installing Oracle XML Gateway and Oracle Workflow with Oracle Applications 11i [ID 152775.1] --> Its for 11i, don't find the same for R12.
Oracle XML Gateway Release Notes, Release 12.1.3 --> does not help giving the information on how to setup XML Gateway
Found the below link but not sure if this is what was asked and looks like Client Desktop Installation.
11i - 12 How To Download and Install the Latest Oracle Workflow Builder (Client Tool) and XML Gateway Message Designer for E-Business (Doc ID 261028.1)
I don't know much about Oracle XML Gateway and how to integrate this to EBS R12, I am not able to find how to integrate this with the existing R12.1.3.
Please someone guide me though this.
Also, I would like to know what benefit could we get with XML Gateway setup when we have the workflows and similar setups already available with R12.1.3, and is there is a way to work out the XML messages inside R12.1.3 without setting up XML Gateway.
Experts please clarify the above and guide me and would highly appreciate for a quick response.
Regards,
Sandy

Hi Sandy,
Did you try the documentation library? The following gives you a detail explanation on how you can setup XML gateway on R12.1.3:
http://docs.oracle.com/cd/B53825_08/current/acrobat/121ecxug.pdf
In addition, also please review notes:
Oracle XML Gateway Release Notes for Release 12.1.3 (Doc ID 1096991.1)
11i - 12 How To Download and Install the Latest Oracle Workflow Builder (Client Tool) and XML Gateway Message Designer for E-Business (Doc ID 261028.1)
Also please review the Forum Search, as this will allow a better understanding.
Forum Search: XML Gateway
Thanks &
Best Regards,

Some RTF commands not working in Oracle XML Publisher Desktop 5.6.3

Hello,
I am using Oracle XML Publisher Desktop 5.6.3 (Patch 5887917) and seems like some of the RTF command are not working. I am following Tim Dexter's blog (http://blogs.oracle.com/xmlpublisher/2007/10/here_are_my_terms_conditions.html ) and could not make the "new" commands from his blog, work in my template.
<?section:force-page-count;'end-on-even-layout'?> -- even with this on the template, I'm still getting output with odd total numpages
<?section:xdofo:blank-on;'even-skip-page-count'?> -- cannot suppress the NUMPAGES value of MS Word
Do I need to apply additional patch(es) on top of Patch 5887917 for the MS Word add-on? Could you please tell me what am I missing?
Thanks.

Hello,
I am trying to install the latest version but getting the error below when performing Preview.
ConfFile: C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\config\xdo.cfg
Font Dir: C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts
Run XDO Start
Template: C:\Documents and Settings\rmembrere\My Documents\MyDelorme\XML Publisher Project\CONVERSIONS\templates\DEL_POs\DEL\PO_TEST_AGAIN.rtf
RTFProcessor setLocale: en-us
RTFProcessor setConfig: C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\config\xdo.cfg
FOProcessor setData: C:\Documents and Settings\rmembrere\My Documents\MyDelorme\XML Publisher Project\CONVERSIONS\templates\DEL_POs\DEL\PO_Sample_2020870.xml
FOProcessor setLocale: en-us
FOProcessor setConfig: C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\config\xdo.cfg
java.lang.reflect.InvocationTargetException
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
     at java.lang.reflect.Method.invoke(Unknown Source)
     at oracle.apps.xdo.common.xml.XSLT10gR1.invokeProcessXSL(Unknown Source)
     at oracle.apps.xdo.common.xml.XSLT10gR1.transform(Unknown Source)
     at oracle.apps.xdo.common.xml.XSLT10gR1.transform(Unknown Source)
     at oracle.apps.xdo.common.xml.XSLTWrapper.transform(Unknown Source)
     at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(Unknown Source)
     at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(Unknown Source)
     at oracle.apps.xdo.template.FOProcessor.createFO(Unknown Source)
     at oracle.apps.xdo.template.FOProcessor.generate(Unknown Source)
     at RTF2PDF.runRTFto(RTF2PDF.java:629)
     at RTF2PDF.runXDO(RTF2PDF.java:439)
     at RTF2PDF.main(RTF2PDF.java:289)
Caused by: oracle.xdo.parser.v2.XPathException: Variable not defined: '_XDONFSEPARATORS'.
     at oracle.xdo.parser.v2.XSLStylesheet.flushErrors(XSLStylesheet.java:1534)
     at oracle.xdo.parser.v2.XSLStylesheet.execute(XSLStylesheet.java:521)
     at oracle.xdo.parser.v2.XSLStylesheet.execute(XSLStylesheet.java:489)
     at oracle.xdo.parser.v2.XSLProcessor.processXSL(XSLProcessor.java:271)
     at oracle.xdo.parser.v2.XSLProcessor.processXSL(XSLProcessor.java:155)
     at oracle.xdo.parser.v2.XSLProcessor.processXSL(XSLProcessor.java:192)
     ... 15 more
Anybody who has used the commands (page suppression) provided by Tim in his blog? May I know from what version you have done it? The blog was posted back in 2007.
Thanks!

Compiler error "oracle.xml.parser.v2.XMLElement" not found in class com.ora

Compiler error "oracle.xml.parser.v2.XMLElement" not found in class com.oracle.demos......?
I am currently testing a simple sample application with a java code similar to the one shown at
the bottom of this post.
However during deployment/compilation the compiler gives an error:
Error(26,23): XMLElement not found in class com.oracle.demos.orderbooking.ApproveImpl
Additionally similar other errors appear:
Error(23,66): JAXBException not found in class com.oracle.demos.orderbooking.ObjectFactory
Error(51,58): UnmarshalException not found in class com.oracle.demos.orderbooking.ObjectFactory
Error(9,92): Element not found in interface com.oracle.demos.orderbooking.Approve
What's wrong?
It seems to me that I have to add some (more) *.jar files/libraries to the project?
Which *.jars and where should I add them in JDeveloper?
source code:
package com.oracle.demos.orderbooking;
public class ApproveImpl extends com.oracle.demos.orderbooking.ApproveTypeImpl implements com.oracle.demos.orderbooking.Approve
public ApproveImpl(oracle.xml.parser.v2.XMLElement node)
super(node);
}

Hai James this the response I am getting can you please tell what should I write inside ora:getNodeValue() to get the value of node <genReturnText>
The drag and dropping the variable name is not working, I have to write the path manually but I dont know how.
<ns1:getRoutingAndFrameJumpersResponse xmlns:ns1="com.NetworkInstallations">
-<com.GetRoutingAndFrameJumpersOutput>
<destination>
SW
</destination>
<e2EData>
busProcOriginator
</e2EData>
<genReturnCode>
40777
</genReturnCode>
<genReturnText>
EMW_Get_Routing_And_FrameJumpers_Succeeded
</genReturnText>
<supplCode>
ISY002
</supplCode>
<supplText>
Transaction successfully completed.
</supplText>
<severityCode>
S
</severityCode>
<retriable>
false
</retriable>
</com.GetRoutingAndFrameJumpersOutput>
</ns1:getRoutingAndFrameJumpersResponse>

Oracle xml DB and text features are not installed

HI,
I installed Sql developer 3.0 ,oracle 11g and jdk 7 on centos 5.when iam running sql developer its showing error message oracle xml DB and text features are not installed.
pls anyone help me out.
thanks
srinivas
Edited by: srinivas on Oct 17, 2011 4:49 AM

may be help you
Re: Connection Error - Oracle XMLDB and Text Features are not installed.

PC Suite does not handle properly messages longer ...

Phone: Nokia 6610i connected with infrared
System Information from PC Suite:
Operating system:
Microsoft Windows XP
Build 2600
Service Pack 2
Language: Italiano
Language for non-Unicode programs: Italiano
Locale: Italiano
Input language: Italiano
Nokia PC Suite:
Version 6.82.22.0
Language: English
Connectivity Cable Drivers:
Not installed
PC Connectivity Solution:
Version 6.43.9.0
I have some messages longer than 160 characters and it seems that they are not handled properly:
- The backup application stops copying messages when it finds the first long message.
- When I browse the messages in Explorer (launched by clicking "Messages" in PC Suite) only sms up to 160 characters are shown. There are also some blank entries in place of long messages.
I've noticed the same problem in the Italian version, I removed it and installed the English version before reporting the issue.
Thanks

Hi read my issue from a few days back from dave100. It seems we are having the same issue. I wroth to support but no one has got back to me. I bet they are clueless and have no idea why this is happening....Check out my attachment. Is yours the same?
cheers.
Dave
Attachments:
empty texts.txt ‏11 KB

Oracle XML processor is not handling variable properly

Similar Messages

Maybe you are looking for