XSLT PARSER

Hi
Do we have any xslt parser kind of support in Flex? I want to
parse an xslt file and render the results in flex datagrid.
Thanks

No.
You might google to see if anyone has buillt an AS3 library
for this but I have not heard of one.
Tracy

Similar Messages

  • How to use document() function in PL/SQL XSLT parser ?

    The "XDB Developers Guide" documentation says on page 12-18
    >
    The application can use DBUriType objects:
    To make references, such as import or include, to related XSL stylesheets. You can encode these references within the XSL stylesheet itself.
    following this i added string like this to my stylesheet
    <xsl:apply-templates select="document('/ORADB/SCOTT/STYLESHEET_TAB/ROW[ID=1]/STYLESHEET/text()')" mode="include"/>
    <xsl:cinclude href="/ORADB/SCOTT/STYLESHEET_TAB/ROW[ID=1]/STYLESHEET/text()"/>
    But when XSLT processor reaches this, it fails.
    I also even tried like this
    <xsl:include href="/ORADB/SCOTT/STYLESHEET_TAB/ROW[ID=1]/STYLESHEET/text()"/>
    but result is the same ;(((
    Generally - is there ANY way XSLT processor can deal with stylesheet which contains
    DBURI references to another stylesheets stored in XMLTYPE columns ?
    I'm currently in charge to develop a content management system for a huge corporate site,
    so i'm VERY interested to know - does this feature really exists on Oracle 9.2 ?
    Please ansver ASAP.

    BTW: following this link
    xsl:include within XSL stylesheet stored in XMLType column
    i've encountered that this theme has been asked but none from Oracle staff has answered on it yet ;(((((((

  • Outputting XML carriage return in HTML via XSLT

    Hi,
    I have a scenario where I execute a View Object query in ADF to retrieve results from a particular table in the Database. I then iterate through the results in my Java managed bean and manually construct an XML file with all the appropriate tags. I then pass the XML file through a Transformer class in the Java bean based on an XSLT I have created to produce an HTML page. However I have an issue when it comes to handling carriage returns. One of the database table columns can contain carriage returns within its value but in the final HTML page the carriage returns don't have any effect and the text just displays on one line.
    In the database, the values are stored with the carriage return and in SQL Developer, Toad etc this can be seen e.g. Text1 Text2 Text3 Text4 will display on separate lines. In the XML, the carriage return seems to still be there as when I open the file my element which contains the carriage returns shows each part on a new line e.g. <textElement>Text1
                                                           Text2
                                                           Text3
                                                           Text4</textElement>     (The Text2, Text3 and Text4 all start on a new line at the beginning and there's no prior white space as shown in this post)
    The XML file in JDeveloper also shows carriage return arrow symbols where there is one.
    The HTML page just shows them as Text1 Text2 Text3 Text4 all on one line. Inspecting the source of the HTML shows that the carriage return is in fact there as it also displays as per the XML with the values on separate lines.
    Outputting the value from the View Object in Java to the log shows the value coming out like this - Text1 Text2Text3Text4, which is strange but I know the carriage returns are there so I'm not too fussed about this.
    I have tried escaping the characters in the Java by doing str.replaceAll("[\\r\\n]", ""); (but replacing the "" with &#xD; &#xA; or &x0A;) so in the XML it replaces carriage returns and line feeds with these escaped characters. However, when the XSLT parses the XML it doesn't pick these up and instead actually outputs these actual characters as they are e.g. Text1&x0A;Text2&x0A;Text3&x0A;Text4
    So I can confirm that the carriage return is carrying all the way through to the XSL but I can't help but think that maybe I need to do something in the XSL to process this somehow, e.g. doing the equivalent of the 'replace' in Java but I don't know what I need to search for in the XML and also what to actually replace it with..Do I just replace it with a </BR> in HTML?
    We also parse the XML using PDF and Excel XSL Transformer class and see the same results.
    Any help would be appreciated.
    Thanks

    That's a very commonly asked question.
    HTML doesn't preserve linefeeds, except for the <pre> tag.
    You'll have to replace those characters with <BR/> tags in the XSLT.
    Search the Internet for terms like "XSLT HTML LF", you'll find some XSLT sample templates to handle the replacement.

  • DOCTYPE and xslt mapping

    Hi All,
    I have an XSLT mapping.  I have only now found out that I need to include a
    <i><!DOCTYPE Order SYSTEM "XCBL3.0.dtd"></i> tag on the second line of the xml I am sending via HTTP.  This causes the XSLT mapping to fail in XI.  From reading other threads, I understand there is a limitation on the XI xslt parser with "DOCTYPE" tags.
    I have tried a workaround by invoking a custom java program in my xslt mapping to insert the doctype but this gets sent out via HTTP as:
    &lt;!DOCTYPE Order SYSTEM "XCBL3.0.dtd"&gt;
    Is there any other workaround I could do without having to completely rewrite my mapping into a Java mapping as mentioned in another thread?
    Please Help!!

    In your xslt mapping place the following line before the top level element is written
    <xsl:text disable-output-escaping="yes">&lt;!DOCTYPE Order SYSTEM "XCBL3.0.dtd"&gt;</xsl:text>
    Regds Doug.

  • XSLT 2.0 supported in Oracle BPEL ?

    Hi,
    is XSLT 2.0 (schema-aware) supported or is there any way to change the built-in XSLT parser to Saxon or another one?
    Thanks.

    For anyone that's interested, I found the solution.
    In order to make it work, I had to add dateTime() around the XPath locations to the vars:
    <xsl:value-of select="dateTime(/ns1:durationTestProcessRequest/ns1:date2) - dateTime(/ns1:durationTestProcessRequest/ns1:date1)"/>

  • Why don't standard XPath functions work in XSLT?

    I'm having a lot of trouble trying to do some simple string processing in XSLT. What I would like to do is make selection using the standard xpath functions defined by the w3c. I'm using this as my cheat sheet:
    http://w3schools.com/xpath/xpath_functions.asp
    I've tried the default XSLT parser that comes with Java, the latest distro of Xalan and the latest distro of Saxon. Nothing seems to recognize the fn namespace:
    xmlns:fn="http://www.w3.org/2005/02/xpath-functions"
    In particular, I'm trying to use the tokenize(string, regex) function. Only Xalan seems to support this at all, only recognizes {http://xml.apache.org/xalan}tokenize, and it is treating the regex as a literal.
    This is very frustrating. Is it possible to get the standard Xpath functions to work for XSLT?

    How did you get it to work with Saxon? I have saxon9he.jar on my classpath. When I try to transform this:
    <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
        xmlns:src="http://xml.kitfox.com/schema/game/tileWorld/textTable"
        xmlns:xalan="http://xml.apache.org/xalan"
        xmlns:fn="http://www.w3.org/2005/02/xpath-functions"
        version="1.0">
        <xsl:output method="text"/>
    <xsl:template match="/">
        <xsl:for-each select="fn:tokenize('a b c', '\s+')">
            "<xsl:value-of select="."/>"
        </xsl:for-each>
    </xsl:template>
    </xsl:stylesheet>I get the error
    Error on line 100
      Cannot find a matching 2-argument function named
      {http://www.w3.org/2005/02/xpath-functions}tokenize()Is there some other jar you need to include to get http://www.w3.org/2005/02/xpath-functions to resolve?

  • Check XML file against XSD? Via XSLT?

    Hello,
    we´re using a 6.20 system (XI not available) and want to check XML files against a XML-schema definition file (xsd).
    Is there a function in 6.20 available for this? Is it possible to use "CALL TRANSFORMATION" for it? I´ve seen other XSLT parser in the internet which are able to check a source XML against an XSD before transforming it to the result XML.
    But is this possible with an 6.20 system?
    Thank you for your help,
    best regards,
    Stefan

    Here is the sample XML and the schema.
    XML:
    <?xml version="1.0" encoding="UTF-8"?>
    <book isbn="0836217462">
    <title>
      Being a Dog Is a Full-Time Job
    </title>
    <author>Charles M. Schulz</author>
    <character>
      <name>Snoopy</name>
      <friend-of>Peppermint Patty</friend-of>
      <since>1950-10-04</since>
      <qualification>
        extroverted beagle
      </qualification>
    </character>
    <character>
      <name>Peppermint Patty</name>
      <since>1966-08-22</since>
      <qualification>bold, brash and tomboyish</qualification>
    </character>
    </book>
    XSD:
    <?xml version="1.0" encoding="utf-8"?>
    <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
      <xs:element name="book">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="title" type="xs:string"/>
            <xs:element name="author" type="xs:string"/>
            <xs:element name="character" minOccurs="0" maxOccurs="unbounded">
              <xs:complexType>
                <xs:sequence>
                  <xs:element name="name" type="xs:string"/>
                  <xs:element name="friend-of" type="xs:string" minOccurs="0"
                          maxOccurs="unbounded"/>
                  <xs:element name="since" type="xs:date"/>
                  <xs:element name="qualification" type="xs:string"/>
                </xs:sequence>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
          <xs:attribute name="isbn" type="xs:string"/>
        </xs:complexType>
      </xs:element>
    </xs:schema>
    - Suman

  • Java extensions to XSLT

    Hi,
    I'm just starting with the new features in the XML/XSLT parser.
    I would like to use the Java extensions to do something like
    this: I want to be able to insert an XML document at a certain
    position based on user input. I have tried something like
    <xsl:template match="page">
    <xsl:variable name="myparser" select="parser:new()"/>
    <xsl:value-of select="parser:parse
    ($myparser, 'file:/D:/Razvan/OracleXMLParser/sample/prefs.xml')"/
    >
    <xsl:variable name="mydocument" select="parser:getDocument
    ($myparser)"/>
    This is the line ------V
    <xsl:value-of select="$mydocument"/>
    <xsl:apply-templates/>
    </xsl:template>
    and it doesn't work.
    Any ideas?
    Thanks,
    Razvan
    null

    Dear Sateesh,
    Declare xlst variables at start of xsl program like below
                             <xsl:output method="xml" indent="yes"/>
         <xsl:variable name="today_formatted" select="java:java.text.SimpleDateFormat.new('yyyyMMdd')"/>
         <xsl:variable name="time_formatted" select="java:java.text.SimpleDateFormat.new('HHmmss')"/>
          and use them in xsl mapping
    <xsl:value-of select="substring(concat(java:format($today_formatted, $date),$blanks),1,8)"/>
    <xsl:value-of select="substring(concat(java:format($time_formatted, $date),$blanks),1,6)"/>
    thanks,
    madhu

  • Help! XSLT

    I have been searching Oracle sites for 2 days on XSLT. I am writing an interface (over 20 actually) What I want to do is generate xml fragments and zip them together dynamically. The XSLT isn't necessarily the difficult part, just getting Oracle to do it from xmltype variables instead of files on disk. Am I going to have to write java classes to do this?

    Thanks for your reply pepijn. Unfortunately, that doesn't work. This is a sample of that solution:
    DECLARE
    targetxml sys.xmltype;
    sourcexml sys.xmltype;
    xsltsrc sys.xmltype;
    reslt VARCHAR2(4000);
    BEGIN
    newxml := xmltype.createxml('<HELLO>Hello World</HELLO>');
    SELECT msg_txt INTO sourcexml FROM interface_messages WHERE interface_msg_seq_no = 1459550; -- XML source
    xsltsrc := xmltype.createxml('<xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">'||
    ' <xsl:output method="xml" indent="yes"/>'||
    '<xsl:template match="/">'||
    ' <xsl:copy>'||
    ' <xsl:copy-of select="document(sourcexml)/*" />'||
    ' <xsl:copy-of select="document(targetxml)/*" />'||
    ' </xsl:copy>'||
    '</xsl:template>'||
    '</xsl:stylesheet>');
    sourcexml := newxml.transform(xsltsrc);
    reslt := sourcexml.getstringval(); -- print the result
    dbms_output.put_line(substr(reslt, -1, 255));
    END;
    This throws Ora - 30625 method dispatch on a NULL SELF argument. In other words, sourcexml was null. What I want to happen is take sourcexml and merge/add newxml to it using the xslt. The xml selected from the table is just a sample xml. What I want (need) to do is generate xml (select xmlelement(....)) in several segments and depending on the requirements assemble them together. XSLT appears to be the best method, but Oracle's XSLT parser only reads files. and the transform function and method take only 1 xml parameter.
    Sigh!
    Dean

  • TOC built on import using XSLT

    Hello,
    I am working on a FM application which modifies the XML via preprocessing XSLT.
    This includes building a full TOC on the front matter which contains hyperlinks to all the top level chapter titles via unique id's @idref on the TOC/TOC-entry-1/TOC-ref element.
    However, when the front matter FM is generated, the structure view does not show the idref attribute and therefore an empty TOC.
    Is there a way of refreshing the .FM file somehow to reflect the new structure and show the TOC entries ?
    Thanks,
    Andy

    Van,
    As I have inherited this FM appliction, I do not want to change too much. My task was to simply change the page sizes within a particular template which I have done. The only thing I had to alter was the leader dot length, otherwise I altered nothing else.
    Everything is working OK apart from this top level TOC. It's part of a book where the XSL does modify the <TOC-ref> element to populate the idref attribute with the target id.
    Meanwhile, I ran the XSLT on it through Oxygen as you suggested, and the idref is certainly being populated as follows :
    <TOC-entry-1><TOC-ref idref = "D-GA-000047.1" format="TOC-1"/></TOC-entry-1>
    The target id is external.
    As mentioned the structure view does not show these attributes. Just TOC-ref followed by <WHITESPACE>.
    Apparently, according to the customer, this TOC did work before. The original app was compiled using FM8, and I have generated the new templates in FM10. I subsequently upgraded the Read/Write rules and the EDD to reflect FM10 thinking this may be the answer but still not working.
    OR, perhaps it's something to do with the XSLT parser version ? Does this need specifying or does FM use a standard version.
    I had to specifically set it to Saxon6.5.5 within Oxygen to get it working.
    Thanks,
    Andy

  • Saxon parser - use in OSB/ALSB

    Hi All,
    We are considering use saxon to replace Oracle/BEA's internal xslt parser to increase performance , i would like to know if anybody has experience with this.
    As when i change to use saxon i also get following exception.
    Throwable: javax.xml.stream.FactoryConfigurationError: Provider null could not be instantiated: java.lang.NullPoin
    terException
    Stack Trace:
    javax.xml.stream.FactoryConfigurationError: Provider null could not be instantiated: java.lang.NullPointerExceptio
    n
    at javax.xml.stream.FactoryFinder.newInstance(FactoryFinder.java:75)
    at javax.xml.stream.FactoryFinder.find(FactoryFinder.java:136)
    at javax.xml.stream.FactoryFinder.find(FactoryFinder.java:92)
    at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:136)
    at weblogic.descriptor.DescriptorReader.<init>(DescriptorReader.java:22)
    at weblogic.management.provider.internal.ConfigReader.<init>(ConfigReader.java:71)
    I have done following,
    1.copied saxon libraries in $JAVA_HOME/jre/lib directory
    2.created jaxp.properties in $JAVA_HOME/jre/lib
    javax.xml.transform.TransformerFactory=net.sf.saxon.TransformerFactoryImpl
    Rgds

    Hi Anuj,
    As per standard way to plugging in xslt parser i tried to add jaxp.properties.
    Although there is another way in weblogic server uising xml registry to override the default parse and this way i succeeded in replacing weblogic default xslt parser.
    However ALSB has its own implementation of XSLT parser which is part of sb_core.jar , this following class most likely com.bea.wli.sb.stages.transform.TransformFactoryImpl.
    We would like to use our own parser as XSLT engine has a bug.
    If a xpath function is used in XSLT resource(like concat, string-join) , then XSLT fails to execute , this bug is there from Weblogic 9.2 MP2 (ALSB 2.6.1) onwards [ in Weblogic 9.2 MP1 this  works properly].
    So we wanted to change ALSB's default xslt parser to saxon, which is supposed to be best one available.
    We do have case against this bug too ,and we hope we will get a patch .
    Still we want to know if we can replace ALSB's default XSLT engine.
    Rgds
    Roy

  • Possible "Out of memory" error  during XSLT ?

    Hi ,
    I am working on 11gR1.
    In my project I am reading a file in batches of ten thousand messages.
    The file is getting read and archived and I can see expected number of instances getting created in the console.
    But nothing useful is visible inside the instance as the link for BPEL process is not appearing.
    (I have kept audit level as production but even in this case, atleast link should appear)
    When I checked the logs , it indicated that transaction was rolled back due to out of memory error.
    Just before this error, there is a reference to the xsl file which I am using :
    [2010-12-13T08:42:33.994-05:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.bpel.engine.xml] [tid: pool-5-thread-3] [userId: xxxx] [ecid: 0000InVxneH5AhCmvCECVH1D1XvN00002J,0:6:100000005] [APP: soa-infra] [composite_name: xxxx] [component_name: xxxx] [component_instance_id: 560005] [composite_instance_id: 570005] registered the bpel uri resolver [File-based Repository]oramds:/deployed-composites/xxxx_rev1.0/ base uri xsl/ABCD.xsl
    [2010-12-13T08:46:12.900-05:00] [soa_server1] [ERROR] [] [oracle.soa.mediator.dispatch.db] [tid: or[email protected]e01a3a] [userId: <anonymous>] [ecid: 0000InVuNCt5AhCmvCECVH1D1XvN000005,0] [APP: soa-infra] DBContainerIdManager:run() failed with error.Rolling back the txn[[
    java.lang.OutOfMemoryError
    My question is , is there any limit on how much payload can oracle's xslt parser handle in one go ?
    Is decreasing the batch size only possible solution for this ?
    Please share your valuable inputs ,
    Ketan
    Is there any limit on how many number of the elements xslt parser can handle ?
    I am reading a file in batch of 10 thousand messages per file. (Each recordsa has some 6-8 fields)
    The file is getting picked up but the instance does not show anything.

    > I'm getting out of memory errro during system copy import for Dual stack system (ABAP & JAVA).
    >
    > FJS-00003  out of memory (in script NW_Doublestack_CI|ind|ind|ind|ind, line 6293
    > 6: ???)
    Is this a 32bit instance? How much memory do you have (physically) in that machine?
    Markus

  • 500 Internal Server Error - Channel Monitoring Audit Log

    Hi Experts,
    We are facing an error in the 'Audit Log' of the communication channel monitoring of a File Sender Adapter.
    The channel uses a custom written Java Module which uses XSLT parser internally. The audit log displays the following error:
    500   Internal Server Error
    Error: "Application error occurred during the request processing."
    Troubleshooting Guide https://sdn.sap.com/irj/sdn/wiki?path=/display/jsts/home
    Details: "The WebApplicationException log ID is [4698F300D2C40C2000000000000009AA]."
    This error occurs both when the file is processed successfully or when in error. In case of a positive test case file, we can even see the message reaching Pipeline (SXMB_MONI). But only the audit log does not show the processed steps in the channel monitoring and displays the above error message.
    We have even established that the cause of the error is Java Module (First, we executed by removing our custom Java Module from the module steps and the audit log showed the steps correctly. But by putting the module back in the channel, the error resumed).
    Initially, the error was not coming and we were able to test this properly. But over the time the audit log error started. Now, we are not able to get rid of this even by restarting the channel or restarting the Java stack of the server.
    To me, it seems like a memory issue in the Java Stack.
    Any thoughts?
    Can we find out where to find the details of the WebApplicationException log ID displayed above?
    Thanks,
    Sudheer

    Hello,
    This could be generic but may helo you:
    500 Internal Server Errors
    Description: The server encountered an unexpected condition which prevented it from fulfilling the request.
    Possible Tips: Have a look into SAP Notes u2013 804124, 807000
    Regards,
    Caio Cagnani

  • Using XSL to tranform xml in Livecycle designer es3

    Hi,
    I have a dynamic form (.xdp), an .xml data file binded to it, we need to make many manupulations to the text (the below xml does not have much text to show but that is our purpose)(i.e) to show partial bolds in some sentences etc, we figured out that this is not possible to manipulate the text in XML , so we thought of using XSL to overcome, but here comes the real problem,
    i am starting it with real basic xsl-- used  The option Trnsforming Incomimg data, but when i try to preview the .pdf from the designer it throws
    XSLT parsing error 1011: Parsing Error (1011):
        systemID:  'file:///C:/Users/c-sds/Desktop/ALC/'
        publicID:  ''
        line:    
        column:    !
    Form version is higher than target version. This form may not run properly on target.
    Xml:
    Xml:
    <Correspondance>
    <Header>
    <CaseNo>Record ID:  02/9441926</CaseNo>
    <Barcode>*90002425393011</Barcode>
    <CAOAddress>
    <Name>SOUTHERN</Name>
    <Address>
    <AddressLine1>Linetest2</AddressLine1>
    <AddressLine2>Linetest1</AddressLine2>
    <city>XXXX</city>
    <state>xx</state>
    <zip>xxxxx</zip>
    <Replyzip>xxxxx-xxxx</Replyzip>
    </Address>
    <PhoneNo>412-565-2232</PhoneNo>
    <FaxNo>412-565-5179</FaxNo>
    </CAOAddress>
    <MailDate>Mail Date:  04/05/2013</MailDate>
    <ClientAddress>
    <Name>\b.INTERNET EXPLORER\b0.</Name>
    <PaymentName></PaymentName>
    <AlternateName></AlternateName>
    <Address>
    <AddressLine1>19</AddressLine1>
    <AddressLine2></AddressLine2>
    <city>ASDF</city>
    <state>xx</state>
    <zip>1xxx5</zip>
    </Address>
    <PhoneNo></PhoneNo>
    </ClientAddress>
    </Header>
    <Correspondance>
    my xsl:
    <?xml version="1.0"?>
    <xsl:stylesheet
    xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0" >
    <xsl:template match="Header">
          <xsl:text>CaseNo</xsl:text>&nl;
        <xsl:if test="//Correspondance/Header/CaseNo">
          <xsl:value-of select="//Correspondance/Header/CaseNo"/>&nl;
        </xsl:if>
                </xsl:template>
                </xsl:stylesheet>
    i am just trying ot field by field in xsl but it doest seem to work any way
    Thanks in Advance
    V sri

    Hi,
    I have a dynamic form (.xdp), an .xml data file binded to it, we need to make many manupulations to the text (the below xml does not have much text to show but that is our purpose)(i.e) to show partial bolds in some sentences etc, we figured out that this is not possible to manipulate the text in XML , so we thought of using XSL to overcome, but here comes the real problem,
    i am starting it with real basic xsl-- used  The option Trnsforming Incomimg data, but when i try to preview the .pdf from the designer it throws
    XSLT parsing error 1011: Parsing Error (1011):
        systemID:  'file:///C:/Users/c-sds/Desktop/ALC/'
        publicID:  ''
        line:    
        column:    !
    Form version is higher than target version. This form may not run properly on target.
    Xml:
    Xml:
    <Correspondance>
    <Header>
    <CaseNo>Record ID:  02/9441926</CaseNo>
    <Barcode>*90002425393011</Barcode>
    <CAOAddress>
    <Name>SOUTHERN</Name>
    <Address>
    <AddressLine1>Linetest2</AddressLine1>
    <AddressLine2>Linetest1</AddressLine2>
    <city>XXXX</city>
    <state>xx</state>
    <zip>xxxxx</zip>
    <Replyzip>xxxxx-xxxx</Replyzip>
    </Address>
    <PhoneNo>412-565-2232</PhoneNo>
    <FaxNo>412-565-5179</FaxNo>
    </CAOAddress>
    <MailDate>Mail Date:  04/05/2013</MailDate>
    <ClientAddress>
    <Name>\b.INTERNET EXPLORER\b0.</Name>
    <PaymentName></PaymentName>
    <AlternateName></AlternateName>
    <Address>
    <AddressLine1>19</AddressLine1>
    <AddressLine2></AddressLine2>
    <city>ASDF</city>
    <state>xx</state>
    <zip>1xxx5</zip>
    </Address>
    <PhoneNo></PhoneNo>
    </ClientAddress>
    </Header>
    <Correspondance>
    my xsl:
    <?xml version="1.0"?>
    <xsl:stylesheet
    xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0" >
    <xsl:template match="Header">
          <xsl:text>CaseNo</xsl:text>&nl;
        <xsl:if test="//Correspondance/Header/CaseNo">
          <xsl:value-of select="//Correspondance/Header/CaseNo"/>&nl;
        </xsl:if>
                </xsl:template>
                </xsl:stylesheet>
    i am just trying ot field by field in xsl but it doest seem to work any way
    Thanks in Advance
    V sri

  • Adding extra namespace in the target structure

    Input file (currently generating from existing message mapping)
    <?xml version="1.0" encoding="UTF-8"?>\
    <pData xmlns:xsi="namespace1">
    <Name>name</Name>
    <ListChange>
    <status>Active</status>
    </ListChange>
    </pData>
    Required File
    <?xml version="1.0" encoding="UTF-8"?>\
    <pData xmlns:xsi="namespace1" xmlns="namespace2">
    <Name>name</Name>
    <ListChange>
    <status>Active</status>
    </ListChange>
    </pData>
    To add the extra namespace (xmlns="namespace2") used following ways.
    1.     Using XML Anonymiser bean module
    Still the no change in the output (only accepting one namespace at a time 1/2)
    2.     Using XSLT Mapping as 1st row in interface mapping
    <?xml version="1.0" encoding="UTF-8"?>
    <xsl:stylesheet version="1.0"
    xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
    <xsl:output method="xml" encoding="UTF-8"/>
         <xsl:template match="/pData">
                   <pData xmlns:xsi="namespace1" xmlns="namespace2">
                   <xsl:copy-of select="/pData/Name"/>
                   <xsl:copy-of select="/pData/ListChange/status"/>
              </pData>
         </xsl:template>
    </xsl:stylesheet>
    We are getting the following error
    com.sap.aii.utilxi.misc.api.BaseRuntimeException; Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 54, 65, 73(:main:, row:8851, col:24)
    Any inputs are welcome.

    >
    Jayashri Rade wrote:
    > Input file (currently generating from existing message mapping)
    >
    > ********************************************************
    > <?xml version="1.0" encoding="UTF-8"?>\
    >
    > <pData xmlns:xsi="namespace1">
    >
    > <Name>name</Name>
    > <ListChange>
    > <status>Active</status>
    > </ListChange>
    >
    > </pData>
    > ********************************************************
    > Required File
    > ********************************************************
    >
    > <?xml version="1.0" encoding="UTF-8"?>\
    >
    > <pData xmlns:xsi="namespace1" xmlns="namespace2">
    >
    > <Name>name</Name>
    > <ListChange>
    > <status>Active</status>
    > </ListChange>
    >
    > </pData>
    > ********************************************************
    >
    > To add the extra namespace (xmlns="namespace2") used following ways.
    > 1.     Using XML Anonymiser bean module
    > Still the no change in the output (only accepting one namespace at a time 1/2)
    the bean is to remove namespaces.. not to add
    > 2.     Using XSLT Mapping as 1st row in interface mapping
    > ********************************************************
    >
    > <?xml version="1.0" encoding="UTF-8"?>
    > <xsl:stylesheet version="1.0"
    > xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
    > <xsl:output method="xml" encoding="UTF-8"/>
    >
    >      <xsl:template match="/pData">
    >
    >                <pData xmlns:xsi="namespace1" xmlns="namespace2">
    >                <xsl:copy-of select="/pData/Name"/>
    >                <xsl:copy-of select="/pData/ListChange/status"/>
    >
    >           </pData>
    >
    >      </xsl:template>
    > </xsl:stylesheet>
    > ********************************************************
    > We are getting the following error
    > com.sap.aii.utilxi.misc.api.BaseRuntimeException; Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 54, 65, 73(:main:, row:8851, col:24)
    >
    > Any inputs are welcome.
    the code looks fine. but i prefer a simple java mapping with a string operation to replace the tag <pData xmlns:xsi="namespace1"> to <pData xmlns:xsi="namespace1" xmlns="namespace2">. it will be simple string handling plus you will not lose any performance by using a XSLT parser invoked.

Maybe you are looking for