XSL Version  2.0

Hi there,
does ORACLE intend to support the XSL Version 2.0 when the w3c recommends it?
best regards
Alex

Hi there,
does ORACLE intend to support the XSL Version 2.0 when the w3c recommends it?
best regards
Alex

Similar Messages

  • XSL-1009 XSL:Version

    The following xsl sample will translate with ORAXSL without errors in one of my docs:
    <?xml version="1.0"?>
    <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
    <xsl:import href="../generic/parsePOHeader.xsl"/>
    <xsl:import href="../generic/parsePOLine.xsl"/>
    <xsl:output method="xml" indent="yes"/>
    <xsl:template match="/">
    <xsl:value-of disable-output-escaping="yes" select="'&lt;?soxtype urn:x-commerceone:document:com:commerceone:XCBL30:XCBL30.sox$1.0?&gt;'"/>
    <xsl:element name="Order">
    <xsl:element name="OrderHeader">
    <xsl:call-template name="parsePOHeader">
    <xsl:with-param name="HEADER" select="//POHEADER"/>
    <xsl:with-param name="ProcessPO" select="'Y'"/>
    </xsl:call-template>
    </xsl:element>
    <xsl:if test="count(//POLINE) &gt; 0">
    <xsl:element name="OrderDetail">
    <xsl:element name="ListOfItemDetail">
    <xsl:for-each select="//POLINE">
    <xsl:call-template name="parseLINE">
    <xsl:with-param name="LineItem" select="."/>
    </xsl:call-template>
    </xsl:for-each>
    </xsl:element>
    </xsl:element>
    </xsl:if>
    <xsl:call-template name="createOrderSummary">
    <xsl:with-param name="NumLines" select="count(//POLINE) + count(//POSUBLINE)"/>
    <xsl:with-param name="Amount" select="//POHEADER/OPERAMT[@qualifier='EXTENDED' and @type='T']"/>
    </xsl:call-template>
    </xsl:element>
    </xsl:template>
    </xsl:stylesheet>
    The following xsl with the same stylesheet statement errors out.
    <?xml version="1.0"?>
    <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
    <xsl:import href="../generic/parsePOHeader.xsl"/>
    <xsl:import href="../generic/parsePOLine.xsl"/>
    <xsl:output method="xml" indent="yes"/>
    <xsl:template match="/">
    <xsl:value-of disable-output-escaping="yes"
    select="'&lt;?soxtype
    urn:x-commerceone:document:com:commerceone:XCBL30:XCBL30.so
    x$1.0?&gt;'"/>
    <xsl:element name="Order">
    <xsl:element name="OrderHeader">
    <xsl:call-template name="parsePOHeader">
    <xsl:with-param name="HEADER"
    select="//POHEADER"/>
    </xsl:call-template>
    </xsl:element>
    <xsl:if test="count(//POLINE) &gt; 0">
    <xsl:element name="OrderDetail">
    <xsl:element name="ListOfItemDetail">
    <xsl:for-each select="//POLINE">
    <xsl:call-template name="parseLINE">
    <xsl:with-param name="LineItem"
    select="."/>
    </xsl:call-template>
    </xsl:for-each>
    </xsl:element>
    </xsl:element>
    </xsl:if>
    <xsl:call-template name="createOrderSummary">
    <xsl:with-param name="NumLines"
    select="count(//POLINE) + count(//POSUBLINE)"/>
    <xsl:with-param name="Amount"
    select="//POHEADER/OPERAMT[@qualifier='EXTENDED' and
    @type='T']"/>
    </xsl:call-template>
    </xsl:element>
    </xsl:template>
    </xsl:stylesheet>
    ERROR:
    A nonfatal internal JIT (3.10.107(x)) error 'GetRegisterA' has occurred in :
    'oracle/xml/parser/v2/XSLNodeList.indexOf (Lorg/w3c/dom/Node;)I': Interpreting method.
    Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cgi
    oracle.xml.parser.v2.XSLException: XSL-1016: Extension function namespace should start with 'http://www.oracle.com/XSL/Transform/java/'.
    Error occurred while processing OAGIShowPONeal.xml: XSL-1016: Extension function namespace should start with 'http://www.oracle.com/XSL/Transform/java/'.
    I made the suggested change to the XSL
    <?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="/">.
    And I get the following error:
    Error occurred while processing ORATransformShowPO.xsl: XSL-1009: Attribute 'xsl:version' not found in 'xsl:stylesheet'.
    I searched Technet.oracle.com for an explanation. According to Steve Muench, 7/24/2000, I need to use the following : <xsl:stylesheet version="1.0" xmlns:xsl=" " target="_new">http://www.w3.org/1999/XSL/Transform">
    This makes no sense because it has an odd number of quotes and > symbols but I tried it. I have the same error, again.
    Can anyone make sense of this?
    Big Hurrah for the solution!

    I typed the words "turn off jit" into Google and came up with a link like:
    http://java.apache.org/faq/fom-serve/cache/152.html
    that might help.

  • How to add namespace prefix to root tag in XSL version 1.1  SOA 11g

    Hi Experts,
       Can any one post solution for adding namespace prefix to root tag using XSL version 1.1 in SOA 11g?
    I have tried the below options and none is working.
    1. Removing prefix add in exclude-prefixes in XSL.But still seeing no prefix for root tag.
    2. Added the <xsl-element>   tag with namespace.But it is not working
    3. Added the below XSL code and it is not working.
      <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
       xmlns:ns0="https://api.ladbrokes.com/v1/sportsbook-couchbase/Temp.xsd">
      <xsl:output method="xml" indent="yes" omit-xml-declaration="yes"/>
      <xsl:template match="@* | node()">
       <xsl:copy>
       <xsl:apply-templates select="@* | node()"/>
       </xsl:copy>
      </xsl:template>
      <xsl:template match="/*">
       <xsl:element name="ns0:{local-name()}">
       <xsl:copy-of select="namespace::*" />
       <xsl:apply-templates select="@* | node()" />
       </xsl:element>
      </xsl:template>
    </xsl:stylesheet>

    Try this:
    <xsl:stylesheet  version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
    <xsl:template match="@*|text()|comment()|processing-instruction()">
            <xsl:copy>
                <xsl:apply-templates select="@*|node()"/>
            </xsl:copy>
        </xsl:template>
        <xsl:template match="/">
            <RootTag xmlns:ns0="https://api.ladbrokes.com/v1/sportsbook-couchbase/Temp.xsd">
                <xsl:apply-templates select="@*|node()"/>          
            </RootTag >
        </xsl:template>
        <xsl:template match="*">
            <xsl:element name="{local-name()}">
                <xsl:apply-templates select="@*|node()"/>
            </xsl:element>
        </xsl:template>
    </xsl:stylesheet>

  • Xsl version

    We have following two queries
    1. We are trying to import xml data into Oracle database. For this purpose we are using dbms_xmlsave and other related packages. Our requirement is: We would like to ignore some of the elements/objects in xml while performing the insertXML operation. We do not want to create all the columns and then specify the update property for those. Is there any way by which we can achieve this?
    For ex:
    <Employee>
    <Name>John</Name>
    <Home_address>NY</Home_address>
    <Office_address>
    <Street>Main street</Street>
    <Zip>06905</Zip>
    <State>CT</State>
    </Office_address>
    <Sal>4521</Sal>
    </Employee>
    For this table is:
    employee (name varchar2(20),Home_address varchar2(50))
    How we can update employee table from above xml?
    2. While using stylesheet in xmlparser, we have specified xsl:version="1.0" in xsl:stylesheet. But still it gives us error
    xsl:1009 attribute xsl:version not specified in xsl:stylesheet.
    we have xml namespace as xmlns:xsl="http://www.w3.org/1999/xsl/Transform"

    I typed the words "turn off jit" into Google and came up with a link like:
    http://java.apache.org/faq/fom-serve/cache/152.html
    that might help.

  • Oracle.xml.parser.v2.XSLException: XSL-1009: Attribute 'xsl:version' not found in 'RO

    I'm using the oracle.xml.parser.v2. The files (xml, xsl) are:
    <?xml version="1.0" ?>
    <?xml-stylesheet type="text/xsl" href="king.xsl" ?>
    <ROWSET>
    <ROW>
    <EMPNO>7839</EMPNO>
    <ENAME>KING</ENAME>
    </ROW>
    </ROWSET>
    <?xml version="1.0"?>
    <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
    <xsl:output method="xml" indent="yes"/>
    <xsl:template match="/">
    <INVITATION>
    <TO>
    <xsl:value-of select="ROWSET/ROW/ENAME"/>
    <xsl:text> &; FAMILY </xsl:text>
    </TO>
    </INVITATION>
    </xsl:template>
    </xsl:stylesheet>
    The error is: oracle.xml.parser.v2.XSLException: XSL-1009: Attribute 'xsl:version' not found in 'ROWSET'.
    The files are well formed (tested with XML Spy 3.5). Can you see what's the problem? or is it a bug with the parser?
    help,
    Alberto
    null

    I encountered the same problem. When I change the order of the XML and XSL files, i am the same problem.
    Perhaps it's the environment AIX 4.3.3, JDK IBM 1.2.2 with JIT disable (because when JIT is enable some other problems become)??
    How can i resolve this bug ?
    Thanks.
    null

  • XSL-1009: Attribute 'xsl:version'  not found in 'BatchDelivery'.

    I have seen this error in many postings and have never understood just what was being transgressed. I am trying to prepare an xml file for inserting into a table using OracleXML putXML but I never get that far. I have exhausted all my guesses and interpretations of others' postings.
    C:\oracle\Samples\BatchDelivery>oraxsl -debug batchdelivery.xsl batchdelivery.txt out.xml
    Error occurred while processing batchdelivery.txt: file:/C:/oracle/Samples/Batch
    Delivery/batchdelivery.txt<Line 2, Column 83>: XSL-1009: Attribute 'xsl:version' not found in 'BatchDelivery'.
    C:\oracle\Samples\BatchDelivery>
    batchdelivery.xsl:
    <ROWSET xsl.version="1.0" xmlns:xsl="http://www.w3.org/1999/xsl/Transform" >
    <xsl:for-each select="BatchDelivery/BatchConfiguration">
    <ROW >
    <KEYCONFIGID><xsl:value-of select="KeyConfigID"/></KEYCONFIGID>
    <CARDREQUIREMENTSID><xsl:value-of select="CARDREQUIREMENTSID"/></CARDREQUIREMENTSID>
    <CARDPRODUCTID><xsl:value-of select="CardProductID"/></CARDPRODUCTID>
    <PHYSICALDESCRIPTIONID><xsl:value-of select="PhysicalDescriptionID"/></PHYSICALDESCRIPTIONID>
    <LOGICALDESCRIPTIONID><xsl:value-of select="LogicalDescriptionID"/></LOGICALDESCRIPTIONID>
    <PACKAGECONFIGID><xsl:value-of select="PackageConfigID"/></PACKAGECONFIGID>
    </ROW>
    </xsl:for-each>
    </ROWSET>
    batchdelivery.xml
    <BatchDelivery xmlns="http://www.activcard.com/xml/ns/acms/batch/1.0" xmlns:xsl="http://www.w3.org/2001/XMLSchema-instance"
    xsl:schemaLocation="http://www.activcard.com/xml/ns/acms/batch/1.0/batch_1.0.xsd">
         <Header>
              <DocID>BD-CAC-0000000001</DocID>
              <Date>2001-06-15T00:00:00</Date>
              <Author>Oberthur</Author>
              <Comment>Batch Delivery sample</Comment>
         </Header>
         <DeliveryPlaceInfo>
              <DeliveryPlaceID>OCS-01</DeliveryPlaceID >
              <OrganizationName>Oberthur</OrganizationName>
              <Address>1600 Vault St</Address>
              <City>Storage City</City>
              <ZipCode>33333</ZipCode>
              <State>CA</State>
              <Country>USA</Country>
              <MainContactPerson>
                   <PersonName>joeDoe</PersonName>
                   <Tel1>1-608-578-5000</Tel1>
                   <Tel2/>
                   <Fax/>
                   <Email>[email protected]</Email>
              </MainContactPerson>
         </DeliveryPlaceInfo>
         <CardManufacturerInfo>
              <CardManufacturerID>Oberthur-01</CardManufacturerID>
              <OrganizationName>Oberthur Card Systems</OrganizationName>
              <Address/>
              <City/>
              <ZipCode/>
              <State/>
              <Country/>
              <MainContactPerson>
                   <PersonName/>
                   <Tel1/>
                   <Tel2/>
                   <Fax/>
                   <Email/>
              </MainContactPerson>
         </CardManufacturerInfo>
         <BatchConfiguration>
         <KeyConfigID>0000000002</KeyConfigID>     <CardRequirementsID>0000000001</CardRequirementsID>
         <CardProductID>0000000002</CardProductID>     <PhysicalDescriptionID>0000000001</PhysicalDescriptionID>
              <LogicalDescriptionID>0000000001</LogicalDescriptionID>
              <PackageConfigID>0000000001</PackageConfigID>
         </BatchConfiguration>
    </BatchDelivery>

    I am cursed by the tendency to mistype whenever I repeatedly cut/paste/test/post! Changing the "." to ":" has no affect whatsoever. I wish it did!
    Mike

  • Xslsample error - xsl:version not found in xsl styleshee

    I am getting the following error when running the example
    xslsample. I am able to run the domexample.
    omor>execute xslsample
    ('d:\orant\xdk\plsql\demo', 'family.xml', 'iden.xsl', 'family.out
    ', 'errors.txt');
    Parsing XML document d:\orant\xdk\plsql\demo/family.xml
    Parsing XSL document d:\orant\xdk\plsql\demo/iden.xsl
    The id is5242880
    The id is5242881
    XSL Root element information
    Qualified Name: xsl:stylesheet
    Local Name: stylesheet
    Namespace: http://www.w3.org/XSL/Transform/1.0
    Expanded Name: http://www.w3.org/XSL/Transform/1.0:stylesheet
    A total of 1 XSL instructions were found in the stylesheet
    BEGIN xslsample
    ('d:\orant\xdk\plsql\demo', 'family.xml', 'iden.xsl', 'family.out
    ', 'errors.txt'); END;
    ERROR at line 1:
    ORA-20100: Error occurred while processing: XSL-1009:
    Attribute 'xsl:version' not found in 'xsl:stylesheet'.
    ORA-06512: at "SYS.XSLPROCESSOR", line 22
    ORA-06512: at "SYS.XSLPROCESSOR", line 346
    ORA-06512: at "SYS.XSLSAMPLE", line 59
    ORA-06512: at line 1

    Hi,
    as I wrote in the inital message, we even left out the output method or used "application/pdf". The result is unfortunately always the same. And I still claim this is not a problem with the stylesheet itself, it has to do something with the mobile's environment.
    Something I didn't tell: we have 2 servlets in our application, 1 responsible for output in html and 1 in pdf. The .fo stylesheet passed to the 'html servlet' is parsed correctly (and shows the source code, because it does not know about fo and conversion to pdf), the .xsl stylesheet passed to the 'pdf servlet' raises same exception/same line. You might tell us that there is a problem with the 'pdf servlet', but once again: why in online it is working?
    Greetings and thanx very much for your precious time!

  • XSL-1009: Attribute 'xsl:version' not found in 'xsl:stylesheet'

    I'm just starting to test XML in Oracle 8.1.7 for NT, and received the following error while testing the Oracle provided "xslsample" procedure. I modified the "iden.xls" stylesheet and added version="1.0", but still receive the same error.
    execute xslsample('C:\XML\Sample','family.xml','iden.xsl','family.out','errors.txt');
    Parsing XML document C:\XML\Sample/family.xml
    Parsing XSL document C:\XML\Sample/iden.xsl
    The id is16777216
    The id is16777217
    XSL Root element information
    Qualified Name: xsl:stylesheet
    Local Name: stylesheet
    Namespace: http://www.w3.org/XSL/Transform/1.0
    Expanded Name: http://www.w3.org/XSL/Transform/1.0:stylesheet
    A total of 1 XSL instructions were found in the stylesheet
    BEGIN xslsample('C:\XML\Sample','family.xml','iden.xsl','family.out','errors.txt'); END;
    ERROR at line 1:
    ORA-20100: Error occurred while processing: XSL-1009: Attribute 'xsl:version'
    not found in 'xsl:stylesheet'.
    ORA-06512: at "SCOTT.XSLPROCESSOR", line 22
    ORA-06512: at "SCOTT.XSLPROCESSOR", line 346
    ORA-06512: at "SCOTT.XSLSAMPLE", line 59
    ORA-06512: at line 1
    null

    There is a bug in the demo stylesheet. In iden.xsl the line:
    <xsl:stylesheet xmlns:xsl="http://www.w3.org/XSL/Transform/1.0">should instead be:
    <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">

  • XSL-1009: (Error) Attribute 'version' not found in 'HTML'

    Hi,
    I've got the following problem: oracle.xml.parserv2.XSLException
    <Line 1, Column 7>: XSL-1009: (Error) Attribute '{http://www.w3.org/1999/XSL/Transform}:version' not found in 'HTML'.
    and I wanted to know what are its origins and what to do to go around, knowing that:
    - we run a java application on an oracle 9iAS and it works fine !
    - we run the same application on an oracle web-to-go server and it gives this message on the client when trying to put
    - the mobile server 'java environment' is a little bit never (version) than the online environment, both servers (9ias an mobile) run on the same machine (mobile is never -> impact on client environment? Installs run under jre 1.3.01)
    - we have an xml document (DOM) and an .fo stylesheet (file/url), so no html for output! Where comes it from? The <xsl:output method="html"> has even been removed and tried with method="application/pdf", no change.
    - the function XSLProcessor.newXSLStylesheet raises this exception; to make it at least run on online environment, we used the .jar file from JDevelopper 9.0.2.822 (this .jar is used in JDev, on 9ias and mobile client)
    - the output file (via apache's fop) shows correctly in the online version, but fails the create/use of the stylesheet (tried stylesheet with xml data for output and a generique 'Hello World' .fo for pdf output, both fail)
    - the .fo starts with <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format" version="1.0">
    - we even tried xsl:version="1.0" and no version at all
    - the same XML parsed with an .xsl for html output works fine, in mobile, the attribute "http://www.w3.org/1999/XSL/Transform" does not show up as an error
    I guess we have a version or configuration conflict, but what exactly could it be? If you need some more version numbers, just let me know.
    Thanx very much for any help!

    Hi,
    as I wrote in the inital message, we even left out the output method or used "application/pdf". The result is unfortunately always the same. And I still claim this is not a problem with the stylesheet itself, it has to do something with the mobile's environment.
    Something I didn't tell: we have 2 servlets in our application, 1 responsible for output in html and 1 in pdf. The .fo stylesheet passed to the 'html servlet' is parsed correctly (and shows the source code, because it does not know about fo and conversion to pdf), the .xsl stylesheet passed to the 'pdf servlet' raises same exception/same line. You might tell us that there is a problem with the 'pdf servlet', but once again: why in online it is working?
    Greetings and thanx very much for your precious time!

  • 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"?>
    <!-- this file was generated by the Oracle Migration Workbench Exporter for MS Access 9.2.0.1.0 on 13/02/02 15:16:52 -->
    <!-- Do not modify this file as any modification will invalidate the export and subsequent migration of your MS Access database -->
    <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>

  • Need to modify Standard Purchase Order Stylesheet (PO_STANDARD_XSLFO.xsl)

    Hi
    We need to modify Standard Purchase Order Stylesheet (po_standard_xslfo.xsl) . Current stylesheet generating PO like the following.
    <FOR-EACH>
    ITEM_NUM
    ITEM_DESCRIPTION
    <FOR-EACH>
    SHIP_TO_ADDRESS_LINE1 NEED_BY_DATE QUANTITY
    </FOR-EACH>
    </FOR-EACH>
    Based on this, we are getting the output like this:
    Item Num 1
    Itme Description 1
    Ship To: Needed: Quntity
    1234. A1 Avenue JUL 200
    SomeCity, CA 90706
    1234. A1 Avenue AUG 200
    SomeCity, CA 90706
    4567 B1 Avenue JUL 100
    City2 , CA
    Itme Description 2
    Ship To: Needed: Quntity
    5689. c1 Avenue JUL 200
    SomeCity, CA 90706
    Our requirement is like this:
    Item Num 1
    Itme Description 1
    Ship To: 1234. A1 Avenue, SomeCity, CA 90706
    Month: JUL AUG SEP
    Quantity: 200 200 100
    Ship To: VVV4567 B1 Avenue , SomeCity, CA 90706
    Month: JUL AUG SEP
    Quantity: 100 200 100
    So we need to add ship_to group (ITEM/SHIP_TO) .
    How can we use group by item, ship_to..
    <fo:block> <xsl:value-of select="ITEM_NUM"/> </fo:block>
    <fo:block> <xsl:value-of select="ITEM_DESCRIPTION"/> </fo:block>
    <xsl:for-each select="/PO_DATA/LINES/LINES_ROW/LINE_LOCATIONS/LINE_LOCATIONS_ROW">
    <fo:block> <xsl:value-of select="SHIP_TO_ADDRESS_LINE1"/> </fo:block>
    <fo:block> <xsl:value-of select="substring(NEED_BY_DATE,4,3)"/> </fo:block>
    <fo:block> <xsl:value-of select="QUANTITY"/> </fo:block>
    </xsl:for-each>
    </xsl:for-each>
    In the above code I need split the data by ITEM_NUM/ SHIP_TO_ADDRESS_LINE1.
    I am new to xsl-fo. I tried different ways,but ship_to_address_line1 is generating wiith each quanty and need_by_date.
    Please guide me.
    Thank you
    Raju
    Edited by: subbaraju on May 7, 2009 2:36 PM

    Hi Chandra
    Thank you very much for your suggestion.
    I tried that way, I created some sample xml file, I created sample rtf file and I generated xsl-fo file. I copied the part of code into my PO_STANDARD_PO.XSL. I am getting some error.
    I noticed PO_STANDARD_PO.XSL is xsl version 1.0 and the generated sample data is with xsl version 2.0.
    The generated code is using “for-each_group”, “sum()”, “current-group()” etc. Is these functions will work in xslt 1? Or do we need to code different way?
    We are in Oracle APPS 12.0.4.
    Thank you
    Raju
    Edited by: subbaraju on May 26, 2009 11:56 AM

  • Passing Parameter to XSL document (in XDK forPL/SQL)

    Here i' trying to pass parameters to my XSL document.But the value is not getting populated in the final document, can anyone help me on this.,.?
    // This is how i 'm passing parameter value to the XSL
    xslprocessor.setParam (styles,'p_batch_name','batch1');
    // Applyting stylesheet(xsl) with XMLdoc and storing it in a DOM node
    docn := xmldom.makeNode(xslprocessor.processXSL(engine,styles,doc));
    My XSL is like this
    <INSERT xsl:version="1.0" xmlns:xsl ="http://www.w3.org/1999/XSL/Transform">
    <xsl:param name="p_batch_name"/>
    <ROWSET table="abc">
    <xsl:for-each select="rowset/row">
    <ROW>
    <batch_name>"{$p_batch_name}"</batch_name>
    </ROW>
    <xsl:for-each>
    </ROWSET>
    <INSERT>
    But in the final document, the value (batch1) is not getting
    populated. it is coming as null .
    Can anyone help me ...
    null

    This does not work because of the following two things:
    [list=1]
    [*]The value of a parameter is interpreted as an XPath expression. Passing a value of batch1 will be interpreted as the XPath expression batch1 that will try to match any <batch1> child elements of the root of the source document. You need to include the value in quotes to have it be interpreted as a literal string:xslprocessor.setParam (styles,'p_batch_name','"batch1"');[*] The setParam method can only set the value of "top-level" stylesheet parameters. In your stylesheet, you've illegally used <xsl:param> inside a template. You need to switch from the "simple form" of a stylesheet to the "normal form" of the stylesheet to use a top-level parameter. So instead of:<INSERT>
    </INSERT>
    [code]
    you need instead:
    [code]
    <xsl:stylesheet>
    <xsl:template match="/">
    <INSERT>
    </INSERT>
    </xsl:insert>
    </xsl:stylesheet>[list]
    null

  • Xsl:template in insert-request

    Hi all
    I try to use <xsl:call-template >
    in the transform page that is being call from <xsql:insert-request> but I get an error
    <xsql-error action="xsql:insert-request"><message>XSL-1049: Template '' invoked but not defined.</message></xsql-error>
    i need to call template because I need to run on a string and tokenize it, so I have use to template with recursion
    does anyone has a clue
    null

    hi Jinyu
    the xsl is
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <ROWSET xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xsl:version="1.0">
    <xsl:choose>
    <xsl:when test="string-length(STORIES/STORY/TICKER) >0">
    <xsl:message> before call</xsl:message>
    <xsl:call-template select="tokinze"/>
    <xsl:message> AFTER call</xsl:message>
    </xsl:when>
    </xsl:choose>
    <xsl:template name="tokinze">
    <xsl:message> In Tokinze</xsl:message>
    <ROW>
    <REPOSITORY_ID><xsl:value-of select="concat('reuters','$thedate',../@repository_id)"/></REPOSITORY_ID>
    <SEQ><xsl:value-of select="position()"/></SEQ>
    <RSM_ATTRIBUTE>ticker</RSM_ATTRIBUTE>
    <RSM_VALUE1><xsl:value-of select="../TICKER"/></RSM_VALUE1>
    <RSM_PUBLISH>0</RSM_PUBLISH>
    </ROW>
    </xsl:template>
    </ROWSET>
    and what i need to do is to token the string
    that i get in the TICKER field thats' why i need to use
    recursion
    thanks

  • XML/XSL parser/processor problem

    Can anyone telle why mij code doesn't work
    DECLARE
    XMLdoc CLOB;
    XSLdoc sys.xslprocessor.stylesheet;
    HTMLdoc CLOB;
    HTMLparser sys.xmlparser.parser;
    XSLprocessor sys.xslprocessor.processor;
    DOMdoc sys.xmldom.DOMdocument;
    queryCtx DBMS_XMLquery.ctxType;
    BEGIN
    queryCtx := DBMS_XMLQuery.newContext('select * from scott.emp');
    XMLdoc := DBMS_XMLQuery.getXML(queryCtx);
    DBMS_XMLQuery.closeContext(queryCtx);
    HTMLparser := sys.xmlparser.newparser;
    XSLprocessor := sys.xslprocessor.newprocessor;
    sys.xmlparser.parseclob(HTMLparser,XMLdoc);
    DOMdoc := sys.xmlparser.getdocument(HTMLparser);
    XSLdoc := sys.xslprocessor.newstylesheet(DOMdoc,'http://www.w3.org/TR/WD-xsl');
    sys.xslprocessor.processxsl(XSLprocessor,XSLdoc,DOMdoc,HTMLdoc);
    sys.xslprocessor.freestylesheet(XSLdoc);
    sys.xslprocessor.freeprocessor(XSLprocessor);
    sys.xmlparser.freeparser(HTMLparser);
    END;
    there should be html-output but it gives a error:
    ora-20100 attribute "xsl:version" not found in ROWSET......
    Can anyone help me get this code to wrk
    null

    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Steven Muench ([email protected]):
    It appears that you're trying to use the result of the GETXML() -- which is some XML like <ROWSET>/<ROW> -- as the stylesheet itself.<HR></BLOCKQUOTE>
    but the function XSLdoc := sys.xslprocessor.newstylesheet(DOMdoc,'http://www.w3.org/TR/WD-xsl');
    makes a xsl from a xmldom object or am I wrong in this assumption.
    How would I do it then
    null

  • 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

Maybe you are looking for

  • How to validate date fields in the flash form

    i want to validate the date fields to make sure the values are not greater than today's date and from-date is less than or equal to to-date in the flash form. Does the actionscript have a CF DateDiff function for the validatation? Thanks

  • Understanding ColorSync and printing set-up

    I have spent two days hunting round the net for a simple understanding of how to set up my Konica Minolta Magicolor 5450 printer and my G5 Dual so they can work happily together to produce the outpt I need, specifically in relation to greys (currentl

  • Scope of Check Variation in Missing Part list Production Order

    Hi, I have a problem that While creation or conversion from planned order to production order if i get missing part list i found that Scope of check is as Z6 and ZP (Checking rule).But when when i Release the same production order also am getting mis

  • ASCII character/string processing and performance - char[] versus String?

    Hello everyone I am relative novice to Java, I have procedural C programming background. I am reading many very large (many GB) comma/double-quote separated ASCII CSV text files and performing various kinds of pre-processing on them, prior to loading

  • What is the max number of 3850 switches in a stack

    This doc states 4.  Has there been any change to allow more? http://www.cisco.com/c/en/us/products/collateral/switches/catalyst-3850-series-switches/qa_c67-722110.html