Xsl:import error

Why oracle xmlparserv2 dosen't support <xsl:import href="b.xsl"/>?
What's the error message mean?
"oracle.xml.parser.v2.XMLParseException: Error while processing include XSL file (b.xsl).
at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:205)......
It's working at Xalan or Saxon but not Oracle!

I think the error message is telling you that the visual design surface that simplifies creating transforms doesn't support the <xsl:import>. If you need to use <xsl:import>, and assuming that <xsl:include> (which is quite similar to import) is also not supported, then the only other option is working on the XSLT stylesheet in the source editor.

Similar Messages

Xsl:import and xsl:call-template errors for xslt in mediator (ORAMED-03601)

Hello,
I decided for performance issues with bpel execution to use a mediator instead.
In my requester i have a mediator that justs recieves an xml message, uses an xsl transformation (version 2) on that message and then sends it to the EBS.
The xsl file that's works correctly when used in a bpel process has both <xsl:import..../>and <xsl:call_template.../> tags.
When i tried and used the same xsl in the mediator i get an ORAMED-03601 error:
ORAMED-03601:[Invalid transformer configuration]Unable to create transformer. It could be because of transformation file or configuration issues. Reason : "xsl/Xform_PriceListListABMReqMsg_to_PriceListEBMReqMsg.xsl"Possible Fix:Check log file for any exceptions and contact Oracle Support Services for further help
It works correctly again if i comment/remove all the imports and call-template and incorporate them in the xsl file itself.
Do anyone know if there are some limitations using xsl in a mediator instead of a bpel?

Hi,
I have a problem with call-template. I have passed
sed some parameter with call-template tag and used
that parameter in the conditional check tag <xsl:if>
i am getting the error. Can any body tell how to use
this? I actuall want to dynamically pass the tag name
as the parameter and check the attribute value of the
tag passed in the if condition and then i want to
person some action. How can i do it?
Here is the call-template code:
<xsl:call-template name="selected-unselected">
<xsl:with-param
ram name="currentTag">motor-carrier</xsl:with-param>
</xsl:call-template>
Here is the template definition:
<xsl:template name="selected-unselected">
<xsl:param
m name="currentTag">Quick-Quote</xsl:param>
     <xsl:if test="./{$currentTag}/@selected='true'">
          <xsl:text>checked</xsl:text>
     </xsl:if>
     <xsl:if test="./{$currentTag}/@selected='false'">
          <xsl:text>Unchecked</xsl:text>
     </xsl:if>
</xsl:template>
Here is the sample xml code:
<motor-carrier selected="true"/>
<motor-truck selected="false"/>
<sched-mobile-equip selected="false"/>
Here instead of writing the condition check for every
tag i want to write it once and dynamically pass the
tag name as parameter to the template. If the
attribute of the tag has value true then one message
should be displayed otherwise a different message
should be displayed.try this:
<xsl:template name="selected-unselected">
     <xsl:paramm name="currentTag">Quick-Quote</xsl:param>
     <xsl:if test="./*[name()=$currentTag]/@selected='true'">
          <xsl:text>checked</xsl:text>
     </xsl:if>
     <xsl:if test="./*[name()=$currentTag]/@selected='false'">
          <xsl:text>Unchecked</xsl:text>
     </xsl:if>
</xsl:template>

How to resolve Error: "xsl:import" XSL Element Currently not Supported

Hello Everyone,
I have a xsl in my process to perform transformation of source schema to target schema.
This xsl is importing another xsl.
I am using <xsl:import> for this purpose.
But when I try to see the "design" editor I am getting the error given below:
Error: "xsl:import" XSL Element Currently not Supported
In "source" editor JDeveloper is giving no error.
I request you all to please come forward for the rescue ;-)
Thanks in advance.
Regards,
Shanty

I think the error message is telling you that the visual design surface that simplifies creating transforms doesn't support the <xsl:import>. If you need to use <xsl:import>, and assuming that <xsl:include> (which is quite similar to import) is also not supported, then the only other option is working on the XSLT stylesheet in the source editor.

XSL:Import causing End-Of-Communication error when called in PL/SQL.

I have master xsl. I am importing another xsl in it. when I use xslTransform in my pl/sql stored procedure I receive end of communication error. I have used "file://" and "http://" both in xsl:import.
Here's the import lines:
<xsl:import href="file://D:/temp/Xsd/CommonFunctions.xsl"/>
or
<xsl:import href="http://www.v-tek.com/xsl/CommonFunctions.xsl"/>
I am not sure what causes this error. I tested this in xmlspy and it works well.

Hi Justin,
I tried to reproduce your complaint, but wasnt able to. I didnt have a 10104 db to test against though, but I did test against 10105, and 10202, using the following dumb table:
create table constr_test ( c1 number);
alter table constr_test add constraint const_1 check (c1 in (1,2,null));
insert into constr_test values (3);
commit;
Frequently a 3113 is the result of an ora-600 or ora-7445 on the database. The fact that it doesnt occur for you on 10.2 db leads me to believe that might be the case here. Have you checked your alert logs?
Cheers,
Greg

Using xsl:import and trying to access a variable defined in another xsl

Hi
I am having a a.xsl file with contents liek this :
<xsl:variable name="PersonId" select="'1910'"/>
inside b.xsl i am importing a.xsl like
<xsl:import href="a.xsl"/>
<xsl:value-of select="$PersonId"/>
This is working fine when i am testing it standalone.
when i port the code to weblogic server (meaning when all the
project related files are placed in proper location in
weblogic) and start the application then i get the error msg :
xsl:1031 variable not defined 'PersonId'.
i tried giving the enite path like :http://localhost:7001/....
even then problem remains unresolved.
am i making any mistake ?
Thank you
Regards
Jaya

This works fine for me with Oracle XSL Processor 9.0.2C

<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:variable name="PersonId" select="1910"/>
</xsl:stylesheet>and

<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:import href="a.xsl"/>
<xsl:template match="/">
<xsl:value-of select="$PersonId"/>
</xsl:template>
</xsl:stylesheet>Make sure you're using the latest version of the XDK in your
weblogic environment.

XSL-1047: (Error) Invalid instantiation of 'xsl:output' in 'INSERT' context

Following is my development environment:
JDeveloper 9i Release Candidate
JDeveloper JVM 1.3.1
Oracle XML Parser v2 9.2.0.0.0
I'm using the Oracle XML Parser V2 9.2.0.0.0 library to apply a stylesheet to an XML document. However when I invoke the call to processor.processXSL() an XSLException is thrown with the following details:
oracle.xml.parser.v2.XSLException: <Line 1, Column 116>: XSL-1047: (Error) Invalid instantiation of 'xsl:output' in 'INSERT' context.
exception
Below is the sequence of events:
// Create an instance of XSLProcessor to perform the transformation
XSLProcessor processor = new XSLProcessor();
// create a Reader from a String object that contains the stylesheet text
StringReader r = new StringReader( stylesheet );
// create a new XSL stylesheet, passing it the Reader object reference
XSLStylesheet sheet = processor.newXSLStylesheet(r);
// apply the stylesheet
// the variable sheet represents the XSLStylesheet object
// the variable source represents the XMLDocument object
// this call throws the exception
DocumentFragment df =
processor.processXSL(sheet,source);
I've included the Stylesheet and source XML file I'm processing below.
Note: My application works fine when I use the Oracle XML Parser v2 9.0.1 library. (although I have to use new XSLStylesheet() in place of XSLProcessor.newXSLStylesheet())
Any ideas on what has changed between the two releases? I do have a reproducible test case that I can send on if required?
thanks in advance
private String stylesheet =
"<INSERT xsl:version=\"1.0\" xmlns:xsl=\"http://www.w3.org/1999/XSL/Transform\"> "+
"<xsl:output method=\"xml\" indent=\"yes\"/> "+
"<ROWSET table_name=\"acc_database\"> "+
" <xsl:for-each select=\"DATABASES/DATABASE\"> "+
" <ROW> "+
" <DBID><xsl:value-of select=\"DBID\"/></DBID> "+
" <DBNAME><xsl:value-of select=\"DBNAME\"/></DBNAME> "+
" <DBSIZE><xsl:value-of select=\"DBSIZE\"/></DBSIZE> "+
" <DBPATHNAME><xsl:value-of select=\"DBPATHNAME\"/></DBPATHNAME> "+
" <DBUSER><xsl:value-of select=\"DBUSER\"/></DBUSER> "+
" <DBPASSWORD><xsl:value-of select=\"DBPASSWORD\"/></DBPASSWORD> "+
" <ISAPPDB><xsl:value-of select=\"ISAPPDB\"/></ISAPPDB> "+
" <ISATTACHEDDB><xsl:value-of select=\"ISATTACHEDDB\"/></ISATTACHEDDB> "+
" <CONVERTDB><xsl:value-of select=\"CONVERTDB\"/></CONVERTDB> "+
" <VERSION><xsl:value-of select=\"VERSION\"/></VERSION> "+
" </ROW> "+
" </xsl:for-each> "+
"</ROWSET> "+
"</INSERT>";
<?xml version="1.0" encoding="ISO-8859-1"?>


<DATABASES>
<DATABASE>
<DBID>1</DBID>
<DBNAME>xmltest</DBNAME>
<DBSIZE>1</DBSIZE>
<DBPATHNAME>E:\xmltest.mdb</DBPATHNAME>
<DBUSER>xmltest</DBUSER>
<DBPASSWORD>oracle</DBPASSWORD>
<ISAPPDB>1</ISAPPDB>
<ISATTACHEDDB>0</ISATTACHEDDB>
<CONVERTDB>1</CONVERTDB>
<VERSION>4.0</VERSION>
<TABLES>
<TABLE PRIMARY_KEY="1">
<TBLID>1</TBLID>
<DBID>1</DBID>
<TBLNAME>xsu_test</TBLNAME>
<CNVTABLESTRUCT>1</CNVTABLESTRUCT>
<CNVMOVEDATA>1</CNVMOVEDATA>
<CNVRI>1</CNVRI>
<CNVVALIDATION>1</CNVVALIDATION>
<CNVDEFAULT>1</CNVDEFAULT>
<CNVADDTIMESTAMP>1</CNVADDTIMESTAMP>
<ATTACHTABLEBACKTOACCESS>1</ATTACHTABLEBACKTOACCESS>
<SAVEPASSWORD>0</SAVEPASSWORD>
<CNVMAKEUPDATEABLE>1</CNVMAKEUPDATEABLE>
<RETAINLOCALCOPY>0</RETAINLOCALCOPY>
<SYNCWITHSERVER>1</SYNCWITHSERVER>
<OWNERID>1</OWNERID>
<VALIDATIONTEXT></VALIDATIONTEXT>
<VALIDATIONRULE></VALIDATIONRULE>
<NUMBEROFROWS>1</NUMBEROFROWS>
<CACHINGTABLE>0</CACHINGTABLE>
<DESCRIPTION></DESCRIPTION>
<COLUMNS>
<COLUMN>
<COLID>1</COLID>
<TBLID>1</TBLID>
<COLNAME>id</COLNAME>
<COLTYPE>4</COLTYPE>
<COLTYPEDESC>Long</COLTYPEDESC>
<COLAUTOINCR>1</COLAUTOINCR>
<NEXTCOUNTERVALUE>0</NEXTCOUNTERVALUE>
<MAXLENGTHSOURCE>0</MAXLENGTHSOURCE>
<AVGLENGTHSOURCE>0</AVGLENGTHSOURCE>
<COLTEXTSIZE>4</COLTEXTSIZE>
<ALLOWZEROLENGTH>0</ALLOWZEROLENGTH>
<DEFAULTVALUE></DEFAULTVALUE>
<COLREQUIRED>1</COLREQUIRED>
<COLCOLLATINGORDER>1033</COLCOLLATINGORDER>
<COLORDPOSITION>1</COLORDPOSITION>
<VALIDATIONRULE></VALIDATIONRULE>
<VALIDATIONTEXT></VALIDATIONTEXT>
<COLUMNDESCRIPTION></COLUMNDESCRIPTION>
</COLUMN>
<COLUMN>
<COLID>2</COLID>
<TBLID>1</TBLID>
<COLNAME>name</COLNAME>
<COLTYPE>10</COLTYPE>
<COLTYPEDESC>Text</COLTYPEDESC>
<COLAUTOINCR>0</COLAUTOINCR>
<NEXTCOUNTERVALUE>0</NEXTCOUNTERVALUE>
<MAXLENGTHSOURCE>0</MAXLENGTHSOURCE>
<AVGLENGTHSOURCE>0</AVGLENGTHSOURCE>
<COLTEXTSIZE>50</COLTEXTSIZE>
<ALLOWZEROLENGTH>0</ALLOWZEROLENGTH>
<DEFAULTVALUE></DEFAULTVALUE>
<COLREQUIRED>1</COLREQUIRED>
<COLCOLLATINGORDER>1033</COLCOLLATINGORDER>
<COLORDPOSITION>2</COLORDPOSITION>
<VALIDATIONRULE></VALIDATIONRULE>
<VALIDATIONTEXT></VALIDATIONTEXT>
<COLUMNDESCRIPTION></COLUMNDESCRIPTION>
</COLUMN>
</COLUMNS>
<INDEXES>
<INDEX>
<INDID>1</INDID>
<TBLID>1</TBLID>
<DBID>1</DBID>
<INDNAME>id</INDNAME>
<CNVINDEX>1</CNVINDEX>
<ISPRIMARY>0</ISPRIMARY>
<ISUNIQUE>0</ISUNIQUE>
<ISFOREIGN>0</ISFOREIGN>
<IGNORENULLS>0</IGNORENULLS>
<ISREQUIRED>0</ISREQUIRED>
<INDEX_COLUMNS>
<INDEX_COLUMN>
<INDCOLID>1</INDCOLID>
<INDID>1</INDID>
<COLID>1</COLID>
<COLORDER>1</COLORDER>
</INDEX_COLUMN>
</INDEX_COLUMNS>
</INDEX>
<INDEX>
<INDID>2</INDID>
<TBLID>1</TBLID>
<DBID>1</DBID>
<INDNAME>PK_xsu_test</INDNAME>
<CNVINDEX>1</CNVINDEX>
<ISPRIMARY>1</ISPRIMARY>
<ISUNIQUE>1</ISUNIQUE>
<ISFOREIGN>0</ISFOREIGN>
<IGNORENULLS>0</IGNORENULLS>
<ISREQUIRED>1</ISREQUIRED>
<INDEX_COLUMNS>
<INDEX_COLUMN>
<INDCOLID>2</INDCOLID>
<INDID>2</INDID>
<COLID>1</COLID>
<COLORDER>1</COLORDER>
</INDEX_COLUMN>
</INDEX_COLUMNS>
</INDEX>
</INDEXES>
</TABLE>
</TABLES>
<RELATIONS>
</RELATIONS>
</DATABASE>
<ATTACHED_TABLES>
</ATTACHED_TABLES>
</DATABASES>

Your problem is that your stylesheet is illegal.
You're using the "simple form" of the stylesheet which
is equivalent to having a single root template.
If you use the simple form, you cannot use: <xsl:include>,
<xsl:import>, <xsl:output>, <xsl:param>
or any other <xsl:XXX> element which must be at the "top-level"
of the stylesheet.
The solution is to change from:
<INPUT xsl:version="1.0" xmlns:xsl="...">
   <xsl:output>
</INPUT>.
which is illegal to:
<xsl:stylesheet version="1.0" xmlns:xsl="...">
    <xsl:output>
    <xsl:template match="/">
      <INPUT>
      </INPUT>
    </xsl:template>
</xsl:stylesheet>

XSL transformation with xsl:import generates exceptions

I am using the Schematron's basic XSL file basic-schematron.xsl to validate the XML format of one of our data files. The XSL file looks something like this
================
<xsl:stylesheet
version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:axsl="http://www.w3.org/1999/XSL/TransformAlias">
<xsl:import href="skeleton1-5.xsl"/>
<xsl:template name="process-prolog">
<axsl:output method="text" />
</xsl:template>
==================
But, the validation fails while trying to run the transformation on my Schematron input file using this basic-schematron.xsl with java.lang.NoSuchMethodError:
======= OUTPUT ============
Markup Error: no match attribute on <key> outside <rule>
Exception in thread "AWT-EventQueue-0" java.lang.NoSuchMethodError: GregorSamsa.process$dash$root(Lcom/sun/org/apache/xalan/internal/xsltc/DOM;Lcom/sun/org/apache/xml/internal/dtm/DTMAxisIterator;Lcom/sun/org/apache/xml/internal/serializer/SerializationHandler;ILjava/lang/Object;)V
     at GregorSamsa.applyTemplates()
     at GregorSamsa.applyTemplates()
     at GregorSamsa.transform()
     at com.sun.org.apache.xalan.internal.xsltc.runtime.AbstractTranslet.transform(AbstractTranslet.java:594)
     at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:640)
     at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:279)
     at com.solipsa.xsdvalidator.XSDValidator.validateSchematron(XSDValidator.java:137)
     at com.solipsa.xsdvalidator.XSDValidator.validate(XSDValidator.java:181)
     at com.solipsa.xsdvalidator.XSDValidatorUI.jButton1ActionPerformed(XSDValidatorUI.java:244)
     at com.solipsa.xsdvalidator.XSDValidatorUI.access$300(XSDValidatorUI.java:21)
     at com.solipsa.xsdvalidator.XSDValidatorUI$4.actionPerformed(XSDValidatorUI.java:140)
     at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1849)
     at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2169)
     at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
     at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
     at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:234)
     at java.awt.Component.processMouseEvent(Component.java:5488)
     at javax.swing.JComponent.processMouseEvent(JComponent.java:3093)
     at java.awt.Component.processEvent(Component.java:5253)
     at java.awt.Container.processEvent(Container.java:1966)
     at java.awt.Component.dispatchEventImpl(Component.java:3955)
     at java.awt.Container.dispatchEventImpl(Container.java:2024)
     at java.awt.Component.dispatchEvent(Component.java:3803)
     at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4212)
     at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3892)
     at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3822)
     at java.awt.Container.dispatchEventImpl(Container.java:2010)
     at java.awt.Window.dispatchEventImpl(Window.java:1766)
     at java.awt.Component.dispatchEvent(Component.java:3803)
     at java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:234)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
     at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
============= OUTPUT ==============
I tried the individual JAXP 1.3 for J2SDK 1.4.2 (Using the -Djava.endorsed.dirs JVM param) and tried the JDK 1.5.0_02 which has JAXP 1.3 inbuilt and they all fail.
I tried the above with separate Xalan/Xerces jar files, and then it works fine.
The problem seems to be somthing specific to the JAXP 1.3 environment. I can provide more details, if required. Any help is highly appreciated.

One morning your code woke up and found it had been transformed into a giant insect.
But seriously, here's the name of the method that doesn't exist:GregorSamsa.process$dash$rootIs GregorSamsa your class? Maybe your server has an old version of it which is missing that method? (Or: those $ signs look strange to me, maybe they are a mistranslation of some other character?)

XSL-1009 error in XML to XML using XSL

I'm using XSL to transform one XML format to another using and XSL transform file. I'm initiating this with ORAXSL in.xml transform.xsl out.xml. The XSL file has in it:
<?xml version="1.0"?>
<xsl:stylesheet xmlns:xsl="http://www.oracle.com/XSL/Transform/Java" version="1.0">
<xsl:import href="../generic/parsePOHeader.xsl"/>
<xsl:import href="../generic/parsePOLine.xsl"/>
<xsl:output method="xml" indent="yes"/>
<xsl:template match="/">
ORAXSL gives an error of XSL-1009: Attribute xsl:version not found in XSL:Stylesheet.
Putting an XSL: prefix on the version doesn't help. A search for help on this site had a solution for XSL that create HTML.
Has anyone else solved this problem?

Thanks everyone for th ereply. Yes, I tested the mapping in integration bulider and it works fine. Even the file conversion works fine intermittantly! Sometimes it converts successfully and wrties file to target location and sometimes I get this error. I checkd in sxi_cache and I see the mapping xsl files there. I jus had basis reboot PI server and run some cache commands but still same problem! Also, when I have to files in source directory sometimes it converts both, sometimes one and sometimes both fails! I haveno clue what els to try.
What are adapter nodes and wher can I check for that?
Thanks.
Mithun

Xsl:import or xsl:include for ESB projects ?

I have an XSLT stylesheet transformer in a routing service on the ESB, and it uses an <xsl:import> of another stylesheet. I have forced the auxiliary stylesheet into the project zip for deployment alongside the main stylesheet, but the XSLT engine cannot resolve the imported file, the error is either:
"No protocol" if I just use "foo.xsl"
"FileNotFound if I try "file:foo.xsl"
The XSLT engine should import a relative URI wrt the main stylesheet, but it appears it cannot handle relative URIs, and what it's really expecting is a file: or classpath: protocol.
Any ideas what URI incantation I need for it to locate the imported stylesheet ?
Mik

A bit of reverse engineering of the error message, reveals the shocking fact that I have to use this URI:
<xsl:import href="esb:///ESB_Projects/MyProject_esb/foo.xsl" />
So the stylesheets have to be modified from the original form used outside the ESB, and even changed depending on the project which contains them !
Please tell me there's a better way ?
Mik

Using xsl:import in Weblogic

All,
I have a requirement to import an XSL template into another XSL template and use one of the methods defined in the imported file into this importing file. The problem is that it works perfectly fine if I do this in XMLSPY .. but if I do this thru weblogic it throws me an error and doesnot perform the action.
Would appreciate if someone could suggest what I can do to solve this problem.
Thanks ,
Adarsh

This works fine for me with Oracle XSL Processor 9.0.2C

<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:variable name="PersonId" select="1910"/>
</xsl:stylesheet>and

<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:import href="a.xsl"/>
<xsl:template match="/">
<xsl:value-of select="$PersonId"/>
</xsl:template>
</xsl:stylesheet>Make sure you're using the latest version of the XDK in your
weblogic environment.

DBMS_XSLPROCESSOR and xsl:import

Hi all!
I'm using Oracle 9.2 and DBMS_XSLPROCESSOR to transform my XML to HTML.
I build XML using DBMS_XMLDOM methods, build stylesheet using dbms_xslprocessor.newstylesheet,
then try to transform it using DBMS_XSLPROCESSOR.processXSL.
It work fine. But if I add <xsl:import href="http://server/myPackage.getXSL"/>
(myPackage.getXSL return another XSL) to my original xsl file, then dbms_xslprocessor.newstylesheet
function fails with error:
[1]: (Error): ORA-31011: XML parsing failed ORA-19202: Error occurred in XML processing LPX-00412:
Message 412 not found; product=XDK; facility=LPX ORA-06512: at "XDB.DBMS_XSLPROCESSOR",
line 467 ORA-06512: at "XDB.DBMS_XSLPROCESSOR" ...
Does anybody have any ideas what is wrong ?
Thanks in advance,
Gregory.

Hi all!
I'm using Oracle 9.2 and DBMS_XSLPROCESSOR to transform my XML to HTML.
I build XML using DBMS_XMLDOM methods, build stylesheet using dbms_xslprocessor.newstylesheet,
then try to transform it using DBMS_XSLPROCESSOR.processXSL.
It work fine. But if I add <xsl:import href="http://server/myPackage.getXSL"/>
(myPackage.getXSL return another XSL) to my original xsl file, then dbms_xslprocessor.newstylesheet
function fails with error:
[1]: (Error): ORA-31011: XML parsing failed ORA-19202: Error occurred in XML processing LPX-00412:
Message 412 not found; product=XDK; facility=LPX ORA-06512: at "XDB.DBMS_XSLPROCESSOR",
line 467 ORA-06512: at "XDB.DBMS_XSLPROCESSOR" ...
Does anybody have any ideas what is wrong ?
Thanks in advance,
Gregory.

Not able to use xsl:import in my XSL doc

Hi,
I'm using Oracle 9.2.0.6.0 and DBMS_XSLPROCESSOR to transform my XML.
I build XML using DBMS_XMLDOM methods, build stylesheet using dbms_xslprocessor.newstylesheet,
then try to transform it using DBMS_XSLPROCESSOR.processXSL.
It work fine. But if I add <xsl:import href="new_file.xsl"/> to my original xsl file, then dbms_xslprocessor.newstylesheet
function fails with error:
[1]: (Error): ORA-31011: XML parsing failed ORA-19202: Error occurred in XML processing LPX-00412:
Message 412 not found; product=XDK; facility=LPX ORA-06512: at "XDB.DBMS_XSLPROCESSOR",
line 467 ORA-06512: at "XDB.DBMS_XSLPROCESSOR" ...
Any ideas??
Thanks in advance
Fred

One idea. Do you have the namespace for the new_file.xsl defined?

FDMEE Import error "No periods were identified for loading data into table 'AIF_EBS_GL_BALANCES_STG'

Hi,
We are having trouble while importing one ledger 'GERMANY EUR GGAAP'. It works for Dec 2014 but while trying to import data for 2015 it gives an error.
Import error shows " RuntimeError: No periods were identified for loading data into table 'AIF_EBS_GL_BALANCES_STG'."
I tried all Knowledge docs from Oracle support but no luck. Please help us resolving this issue as its occurring in our Production system.
I also checked all period settings under Data Management> Setup> Integration Setup > Global Mapping and Source Mapping and they all look correct.
Also its only happening to one ledger rest all ledgers are working fine without any issues.
Thanks

Hi,
there are some Support documents related to this issue.
I would suggest you have a look to them.
Regards

How do I convert an excel (2008) document to Numbers? When I drag the Excel document onto the Numbers icon I get, "Import error. The file format is invalid"

How can I convert an Excel (2008) document to Numbers. When I drag the Excel document onto the Numbers icon I get, "Import error. The file format is invalid.

That extension identifies the most current Excel file format, a format that can be opened by Numbers '09 (and by Numbers '08).
A check with Numbers '09 shows it capable of opening .xlsx files when right-clicked (and Numbers chose as the application to open, when double-clicked (if Numbers has been set as the default application to open this type of file, or when dragged to the Numbers icon in the dock.
I see two possibilities for Numbers inability to open it and the message you receive:
1. The file is not actually an Excel file, and the sender has added the .xlsx extension to the filename manually.
2. The file is an Excel file, but has somehow been corrupted.
Have you tried opening the file with a different application? The open source Office suites, OpenOffice.org, LibreOffice and NeoOffice can also open .xlsx files. If they're unable to open this one, that would point toward the file itself being faulty. You can download these applications from their rspective websites, linked in the names above. All request a donation to support future development, but only Neo requires one to have been made recently, and that only for the current release (which won't be necessary to open .xlsx files).
Regards,
Barry

Xsl variable error not explained in earlier thread

Steve,
Thank you so much for your response to my earlier thread, it is difficult to focus on what I am supposed to be doing today, with all the sad news from the east coast.
Re-visiting this variable issue one more time to try understand what is going wrong with this file.
Below is a shortened version of the file plus the output from parsing it with xalan, saxon and oracle's two latest versions. As you see it parses fine with xalan and saxon but errors out with oracle's latest version. Should this be looked at again perhaps?
xml file
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="UtilDataForm.xsl"?>
<page>
<dataform target="News.xsql" submit="SubmitButtonTitle">
<item type="checkboxlist" name="nameOfCheckBoxList" label="CheckBoxList">
<ROWSET>
<ROW><VALUE>4</VALUE><DISPLAY>This</DISPLAY></ROW>
<ROW><VALUE>5</VALUE><DISPLAY>That</DISPLAY></ROW>
<ROW><VALUE>6</VALUE><DISPLAY>The Other</DISPLAY></ROW>
</ROWSET>
</item>
</dataform>
</page>
xsl file
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">

<xsl:template match="dataform">
<xsl:variable name="form-target">
<xsl:choose>
<xsl:when test="@target">
<xsl:value-of select="@target"/>
</xsl:when>
<xsl:when test="./target">
<xsl:value-of select="./target"/>
<xsl:if test="*">?</xsl:if>
<xsl:for-each select="*">
<xsl:value-of select="name(.)"/>
<xsl:text>=</xsl:text>
<xsl:value-of select="."/>
<xsl:if test="position() != last()">
<xsl:text>&;</xsl:text>
</xsl:if>
</xsl:for-each>
</xsl:when>
<xsl:otherwise>
<xsl:text> </xsl:text>
</xsl:otherwise>
</xsl:choose>
</xsl:variable>
<center>
<form method="POST" action="{$form-target}">
<xsl:for-each select="item[@type='hidden']">
<input type="hidden" name="{@name}" value="{normalize-space(.)}"/>
</xsl:for-each>
<table>
<xsl:for-each select="item[@type != 'hidden']">
<tr>
<th align="right"><xsl:value-of select="@label"/></th>
<td>
<xsl:choose>
<xsl:when test="@type='text'">
<input type="text" name="{@name}"
value="{normalize-space(.)}">
<xsl:if test="@size">
<xsl:attribute name="size">
<xsl:value-of select="@size"/>
</xsl:attribute>
</xsl:if>
</input>
</xsl:when>
<xsl:when test="@type='password'">
<input type="password" name="{@name}"
value="{normalize-space(.)}">
<xsl:if test="@size">
<xsl:attribute name="size">
<xsl:value-of select="@size"/>
</xsl:attribute>
</xsl:if>
</input>
</xsl:when>
<xsl:when test="@type='textarea'">
<textarea class="code" rows="5" name="{@name}">
<xsl:if test="@size">
<xsl:attribute name="cols">
<xsl:value-of select="@size"/>
</xsl:attribute>
</xsl:if>
<xsl:value-of select="normalize-space(.)"/>
</textarea>
</xsl:when>
<xsl:when test="@type='list'">
<xsl:variable name="default" select="default"/>
<select name="{@name}">
<xsl:for-each select="ROWSET/ROW">
<option value="{VALUE}">
<xsl:if test="VALUE=$default">
<xsl:attribute name="selected"/>
</xsl:if>
<xsl:value-of select="DISPLAY"/>
</option>
</xsl:for-each>
</select>
</xsl:when>
<xsl:when test="@ty pe='checkboxlist'">
<xsl:variable name="name" select="@name"/>
<xsl:for-each select="ROWSET/ROW">
<input type="checkbox" name="{$name}" value="{VALUE}">
<xsl:if test="SELECTED='Y'">
<xsl:attribute name="checked"/>
</xsl:if>
</input>
<xsl:value-of select="DISPLAY"/>
</xsl:for-each>
</xsl:when>
</xsl:choose>
</td>
</tr>
</xsl:for-each>
</table>
<input type="submit" value="{@submit}"/>
</form>
</center>
</xsl:template>
</xsl:stylesheet>
xalan output
<?xml version="1.0" encoding="UTF-8"?>
<center><form action="News.xsql" method="POST"><table><tr><th align="right">CheckBoxList</th><td><input value="4"
name="nameOfCheckBoxList" type="checkbox"/>This
<input value="5" name="nameOfCheckBoxList"
type="checkbox"/>That
<input value="6" name="nameOfCheckBoxList" type="checkbox"/>The Other
</td></tr></table><input
value="SubmitButtonTitle" type="submit"/></form></center>
saxon output
<?xml version="1.0" encoding="utf-8"?>
<center><form method="POST" action="News.xsql"><table><tr><th align="right">CheckBoxList</th><td><input type="checkbox"
name="nameOfCheckBoxList" value="4"/>This
<input type="checkbox" name="nameOfCheckBoxList" value="5"/>That
<input
type="checkbox" name="nameOfCheckBoxList" value="6"/>The Other
</td></tr></table><input type="submit"
value="SubmitButtonTitle"/></form></center>
oraxsl with xmlparserv2.jar dated 06/19/01 10:09
<?xml version = '1.0'?>
<center><form method="POST" action="News.xsql"><table><tr><th align="right">CheckBoxList</th><td><input type="checkbox"
name="nameOfCheckBoxList" value="4"/>This
<input type="checkbox" name="nameOfCheckBoxList" value="5"/>That
<input
type="checkbox" name="nameOfCheckBoxList" value="6"/>The Other
</td></tr></table><input type="submit"
value="SubmitButtonTitle"/></form></center>
oraxsl with xmlparserv2.jar dated 08/04/01 20:24
file:/W:/workorders/util/UtilDataForm.xsl: XSL-1031: (Error) Variable not defined: 'name'.
oracle.xml.parser.v2.XPathException: Variable not defined: 'name'.
Error occurred while processing W:\workorders\util\FormTest.xsql: file:/W:/workorders/util/UtilDataForm.xsl: XSL-1031:
(Error) Variable not defined: 'name'.
Thank you again for your help!
Ola Kvalvaag
IS Administrator
CT&E Environmental Services Inc.

Yeah!!! It works. Turned out to be a combination of DrKlap's and Martisan's suggestions -- had to change var frame's declaration from JFrame to MyFrame:
    MyFrame frame;Next, created the external class -- but again changed JFrame references to MyFrame:
public class ShowOnExit extends WindowAdapter {
//   JFrame aFrame;
   MyFrame aFrame;
   public ShowOnExit(MyFrame f) {
      aFrame = f;
   public void windowClosing(WindowEvent e)
      System.out.println("Why me???" + aFrame.textArea.getText()); // aFrame here not frame !!!
}This worked. So looks like even though the original code added a WindowListener to 'frame', the listener didn't couldn't access frame's methods unless it was explicitly passed in as a parameter. Let me know if that's wrong.
Thanks again, all.

Xsl:import error

Similar Messages

Maybe you are looking for