Xml namespace and xslt

Hi,
This is a pure xml question. Let me know if there are good forums better suited for this kind of problem.
I receive an xml message with the following format:
<?xml version="1.0" encoding="ISO-8859-1" ?>
<staticMessage xmlns="Static/nme" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="Static/nme ./StaticMessage.xsd">
</staticMessage>I fail to apply transformation when using a stylesheet like:
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="/">
<xsl:value-of select="staticMessage/body/data"/>
</xsl:template>
</xsl:stylesheet>However if I remove the xmlns attribute in the incoming message (xmlns="Static/nme" ) the transformation works correctly.
I do not have a great understanding of namespaces.
Does anyone know if any special declaration needs to be made for the xsl file to work correctly?
Tx,
Mik.

Noticed that declaring a prefix in xsl (xmlns:pre="Static/nme") allows to access nodes or values ( pre:staticData/pre:.../)
But does a prefix need to reference the xml namespace or is it possible to define it as default?
Tx,
Mik.

Similar Messages

Issue with XML namespace and Message structure

Hi All,
I am using Oracle SOA Suite 11.1.1.4. I have SOA web service application one-way messaging wherein I keep receiving messages from the third party. The issue I am facing is with the XML namespaces which conflicts with the third party's message structure. The details are as below.
Our Web-service WSDL*
<schema attributeFormDefault="unqualified" elementFormDefault="qualified"
targetNamespace="http://amb.com/cad/RealTimeService"
xmlns:cad="http://amb.com/cad/RealTimeService"
xmlns:avl="http://schemas.com/asiapac/cad/datamodel/avl/1.0.0"
xmlns:evn="http://schemas.com/asiapac/cad/datamodel/event/1.0.0"
xmlns:uni="http://schemas.com/asiapac/cad/datamodel/unit/1.0.0"
xmlns:dvt="http://schemas.com/asiapac/cad/datamodel/divert/1.0.0"
xmlns:sui="http://schemas.com/asiapac/cad/datamodel/suppinfo/1.0.0"
xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://schemas.com/cad/datamodel/avl/1.0.0"
schemaLocation="AvlCadSchema.xsd"/>
<import namespace="http://schemas.com/cad/datamodel/unit/1.0.0"
schemaLocation="UnitCadSchema.xsd"/>
<import namespace="http://schemas.com/cad/datamodel/event/1.0.0"
schemaLocation="EventCadSchema.xsd"/>
<import namespace="http://schemas.com/cad/datamodel/divert/1.0.0"
schemaLocation="HewsCadSchema.xsd"/>
<import namespace="http://schemas.com/cad/datamodel/suppinfo/1.0.0"
schemaLocation="SupplementalInformationCadSchema.xsd"/>
<element name="AvlAuxData" type="avl:AvlAuxData" nillable="true"/>
<element name="AgencyEvent" type="evn:AgencyEvent"/>
<element name="Diversion" type="dvt:HospitalDiversionMessage"/>
<element name="SupplementalInformation" type="sui:SupplementalInformation"/>
<element name="UnitDetail" type="uni:UnitDetail"/>
</schema>
Using SOAP UI tool a HospitalDiversionMessage Request for the above WSDL will look like*
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:real="http://amb.com/cad/RealTimeService" xmlns:ns="http://schemas.com/cad/datamodel/divert/1.0.0">
<soapenv:Header/>
<soapenv:Body>
<*real*:Diversion>
<ns:Action>?</ns:Action>
<ns:Open>?</ns:Open>

<ns:Location>?</ns:Location>
<ns:Type>?</ns:Type>
<ns:SubType>?</ns:SubType>

<ns:ExpiryTimestamp>?</ns:ExpiryTimestamp>

<ns:Comment>?</ns:Comment>

<ns:ItemNumber>?</ns:ItemNumber>

<ns:Notifications>?</ns:Notifications>
<ns:CreatedTerminal>?</ns:CreatedTerminal>
<ns:CreatedTimestamp>?</ns:CreatedTimestamp>

<ns:ClosedBy>?</ns:ClosedBy>

<ns:ClosedComments>?</ns:ClosedComments>

<ns:ClosedTerminal>?</ns:ClosedTerminal>

<ns:ClosedTimestamp>?</ns:ClosedTimestamp>
</real:Diversion>
</soapenv:Body>
</soapenv:Envelope>
Now the third party sends a HospitalDiversionMessage in this format_
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns0="http://amb.com/cad/RealTimeService" xmlns:ns="http://schemas.com/cad/datamodel/divert/1.0.0">
<soapenv:Header/>
<soapenv:Body>
<ns0:Diversion>
<ns0:Action>?</ns0:Action>
<ns0:Open>?</ns0:Open>

<ns0:Location>?</ns0:Location>
<ns0:Type>?</ns0:Type>
<ns0:SubType>?</ns0:SubType>

<ns0:ExpiryTimestamp>?</ns0:ExpiryTimestamp>

<ns0:Comment>?</ns0:Comment>

<ns0:ItemNumber>?</ns0:ItemNumber>

<ns0:Notifications>?</ns0:Notifications>
<ns0:CreatedTerminal>?</ns0:CreatedTerminal>
<ns0:CreatedTimestamp>?</ns0:CreatedTimestamp>

<ns0:ClosedBy>?</ns0:ClosedBy>

<ns0:ClosedComments>?</ns0:ClosedComments>

<ns0:ClosedTerminal>?</ns0:ClosedTerminal>

<ns0:ClosedTimestamp>?</ns0:ClosedTimestamp>
</ns0:Diversion>
</soapenv:Body>
</soapenv:Envelope>
Questions*
1) I cannot figure out how the SOAPUI tool or SOA substitutes "real" as the namespace prefix for the WSDL based HospitalDiversionMessage and what I need to do at my end to match the message structure as per what the third party needs.
2) I need ns0 namespace prefix to whole of Diversion xml element. Currently it is "real" at top Diversion element and "ns" for its children
Please suggest, I can attach the other imported XSD if need be.
Thanks
Edited by: user5108636 on Jun 13, 2011 6:55 PM
Edited by: user5108636 on Jun 13, 2011 6:57 PM
Edited by: user5108636 on Jun 13, 2011 7:02 PM

Questions
1) I cannot figure out how the SOAPUI tool or SOA substitutes "real" as the namespace prefix for the WSDL based HospitalDiversionMessage and what I need to do at my end to match the message structure as per what the third party needs.The xml namespace suffixes like real and ns0 are just references used by the XML Parsers. For that matter the "real" can be xyz as well.
You dont need to make any changes as long as the xml namespace suffixes refer to the same namespace.
If you see the first soapUI xml and the third party xml have the same namespace references and hence it is not a problem:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:real="*http://amb.com/cad/RealTimeService*" xmlns:ns="http://schemas.com/cad/datamodel/divert/1.0.0">
<soapenv:Header/>
<soapenv:Body>
<*real*:Diversion>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns0="*http://amb.com/cad/RealTimeService*" xmlns:ns="http://schemas.com/cad/datamodel/divert/1.0.0">
<soapenv:Header/>
<soapenv:Body>
<*ns0*:Diversion>
2) I need ns0 namespace prefix to whole of Diversion xml element. Currently it is "real" at top Diversion element and "ns" for its childrenBased on this, logically both the xmls represent the same xml message. And hence you dont need to make any changes.
Please refer to the basics of xml namespaces using the following links:
http://en.wikipedia.org/wiki/XML_namespace
http://zvon.org/comp/r/tut-Namespace.html#Pages~Introduction
Let us know if you still need clarification.
Hope this helps.
Thanks,
Patrick

VerifyError #1025 - default xml namespace and getter function

I have narrowed the problem down to a a few lines. I have
created a simple example of the problem...
// TestClass.as
package {
import flash.events.EventDispatcher;
public class TestClass extends EventDispatcher {
private var _testVar:String;
public function TestClass() {
var testXML:XML = <node1 xmlns="
http://www.testurl.com/"><node2><node3>some
words of wisdom</node3></node2></node1>;
default xml namespace = testXML.namespace("");
_testVar = testXML.node2.node3;
public function get testVar():String {
return _testVar;
// Test.fla - frame 1
import TestClass;
var myTestClass:TestClass = new TestClass();
var someVar:String = myTestClass.testVar;
trace(someVar);
I get the following error...
verify TestClass/get testVar()
stack:
scope: [global Object$ flash.events::EventDispatcher$
TestClass$]
locals: TestClass
0:getlocal0
stack: TestClass
scope: [global Object$ flash.events::EventDispatcher$
TestClass$]
locals: TestClass
1:pushscope
stack:
scope: [global Object$ flash.events::EventDispatcher$
TestClass$] TestClass
locals: TestClass
2:getlocal1
VerifyError: Error #1025: An invalid register 1 was accessed.
at TestClass/get testVar()
at Test_fla::MainTimeline/Test_fla::frame1()
However if I take out the default xml namespace line, and
create a new namespace it will work.
var testNS:Namespace = new Namespace(testXML.namespace(""));
_testVar = testXML.testNS::node2.testNS::node3;
Thoughts??? It's driving me crazy. Thanks in advance...
levi

The attribute should be in the element's namespace. If I run this snippet on the timeline, it outputs the correct values.
var xml:XML =
<xml>
<animal type="sheep" xmlns="http://blabla">
<name>josh</name>
<age>2</age>
</animal>
<animal type="cow" xmlns="http://blabla">
<name>jim</name>
<age>2</age>
</animal>
</xml>
var ns:Namespace = new Namespace("http://blabla");
default xml namespace = ns;
trace( xml.animal.@type ); // OUTPUT: sheepcow

Default xml namespace and attributes

Hi,
I was trying to use default xml namespaces, but came upon something strange.
I got the following piece of xml:
<animal type="sheep" xmlns="http://blabla">
<name>josh</name>
<age>2</age>
</animal>
and the following code
public static var ns:Namespace = new Namespace("http://blabla");
var xml:XML; // xml will be read into this var, not going into details here
public function myfunc():void {
default xml namespace = ns;
trace( xml.animal.@type );
now for some reason, the elements are correctly traversed using the default namespace. But the attribute isn't found. After a bit of debugging, I found that I could only retrieve the attribute when using xml.animal.attribute(new QName("", "type")). Am I doing something wrong here? Why isn't the attribute in the same default namespace as the element?
Kind regards,
Jan

The attribute should be in the element's namespace. If I run this snippet on the timeline, it outputs the correct values.
var xml:XML =
<xml>
<animal type="sheep" xmlns="http://blabla">
<name>josh</name>
<age>2</age>
</animal>
<animal type="cow" xmlns="http://blabla">
<name>jim</name>
<age>2</age>
</animal>
</xml>
var ns:Namespace = new Namespace("http://blabla");
default xml namespace = ns;
trace( xml.animal.@type ); // OUTPUT: sheepcow

Swapping XML Parser and XSLT to Xalan 2.7.0 - Not Working (OC4J 10.1.3)

Hi-
I'm trying to use the latest Xercies/Xalan classes in OC4J 10.1.3 as described in the How-To swap XML Parsers document:
http://www.oracle.com/technology/tech/java/oc4j/1013/how_to/how-to-swapxmlparser/doc/readme.html
What I can see happening is that the oracle.xml shared library is successfully 'turned off', but the xalan libraries are not added. Instead, the default xml classes that are distributed with the JDK become visible. For instance, using a slightly modified version of the index.jsp page from the how-to, I get this result:
------ Output from JSP page ----------------
TransformerFactory Instance: org.apache.xalan.processor.TransformerFactoryImpl
Transformer Instance: org.apache.xalan.transformer.TransformerIdentityImpl
Transformer Version: Xalan Java 2.4.1 (!!)
What I expect is for that last line to say version 2.7.0, which is the version of the xalan.jar included in my shared library (code to add that line to the how-to shown below).
I suspect what is happening is that the class loader is simply not letting a shared library override a system library - to do that you probably need to place the jar files in system endorsed directory.
Has anyone gotten this how-to to work - actually replacing the XML parser/transform classes with the latest Xalan classes? Are you sure it is seeing the current version you placed in the shared library?
Thanks,
Eric Everman
---- My modified getXSLTDetails() method in the index.jsp page of the how-to -------

<%@ page import="org.apache.xalan.Version" %>
public static String getXSLTDetails()
Transformer transformer=null;
TransformerFactory transformerfactory = TransformerFactory.newInstance();
     Version ver = null;
     String br = "<" + "br" + ">"; //otherwise the otn forum chocks on the break.
try
transformer = transformerfactory.newTransformer();
          ver = (Version) transformer.getClass().forName("org.apache.xalan.Version").newInstance();
          String ret_val =
               "TransformerFactory Instance: "+transformerfactory.getClass().getName() + br +
               "Transformer Instance: "+transformer.getClass().getName() + br;
          if (ver != null) {
               ret_val = ret_val + "Transformer Version: " + ver.getVersion() + br;
          } else {
               ret_val = ret_val + "Transformer Version not Available" + br;
          return ret_val;
catch (Exception e)
e.printStackTrace();
return e.getMessage();
}--------------------------------------------------------------------

Steve - Thanks for responding on this.
The Xalan SQL extension is built into Xalan. The most painless way to try it out is to run it via JEdit: www.jedit.org
JEdit a OS Java application with a fairly painless install process (I'm assuming you already have a current JRE installed). Once its installed, you'll need to install the XSLT plugin - in JEdit goto Plugins | Plugin Manager | Install and pick the XSLT plugin. You'll need the Oracle JDBC classes on your classpath - this can be done by copying the oracle_jdbc4.jar into the [JEdit install directory]/jars directory.
Restart to load that jar and you should be all set.
I included a sample XSLT page at the bottom of this post that is somewhat of a template transform for the SQL extension - its more complicated then it needs to be, but it does some nice things with the results of the query. Save it as a file and make the appropriate changes to the 'datasource' parameter near the top of the file.
Then in JEdit, open the file and make sure the XSLT plugin is visible (Plugins | XSLT | XSLT Processor Toggle - or alternately dock it in the window via global prefs). In the XSLT plugin: Allow the current buffer to be used as the source, Add that same file as a stylesheet via the '+' button, and pick a result file at the bottom. Then click the 'Transform XML' button.
Troubleshooting: I seem to remember having some classpath errors when I tried this on windows, but others have had it work w/o issues. I do remeber that the XSLT plugin had a popup window that gave a pretty good explaintion of the problem, if it occurs. Also, for some reason the XSLT plugin will not create a new file for the output, so its often best to create a file first, then choose it as the output. Of course, you can always run a transformation from the command line or w/in an applicatoin. Full docs on the Xalan SQL extension can be found at: http://xml.apache.org/xalan-j/extensionslib.html#sql
Here is my sample XSLT transform using the SQL extension:
<?xml version="1.0" encoding="UTF-8" ?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
          xmlns:sql="http://xml.apache.org/xalan/sql"
          xmlns:str="http://exslt.org/strings"
          xmlns:xalan="http://xml.apache.org/xalan"
          extension-element-prefixes="sql str xalan">
     <xsl:output indent="yes"/>
     <xsl:param name="driver">oracle.jdbc.OracleDriver</xsl:param>
     <xsl:param name="datasource">jdbc:oracle:thin:jqpublic/jqpublic@server_name:1521:dbname</xsl:param>
     <xsl:param name="jndiDatasource"></xsl:param>
     <xsl:param name="debug">true</xsl:param>
     <xsl:variable name="connection" select="sql:new()"/>
     <xsl:variable name="uppercase" select="'ABCDEFGHIJKLMNOPQRSTUVWXYZ'"/>
     <xsl:variable name="lowercase" select="'abcdefghijklmnopqrstuvwxyz'"/>
     
     <xsl:param name="query">
     select * from (
SELECT
          'One' FIELD_1,
          'Two' FIELD_2
     FROM DUAL
     ) where rownum < 100
     </xsl:param>
     
     <xsl:variable name="connection" select="sql:new()"/>
     <xsl:template match="/">
    <xsl:choose>
      <xsl:when test="$jndiDatasource != ''">
        <xsl:if test="not(sql:connect($connection, $jndiDatasource))">
          <xsl:message>Failed to connect to db via jndi connection</xsl:message>
          <xsl:comment>Failed to connect to db via jndi connection</xsl:comment>
          <xsl:if test="$debug = 'true'">
            <xsl:copy-of select="sql:getError($connection)/ext-error"/>
          </xsl:if>
        </xsl:if>
      </xsl:when>
      <xsl:otherwise>
        <xsl:if test="not(sql:connect($connection, $driver, $datasource))">
          <xsl:message>Failed to connect to db via driver/url connection</xsl:message>
          <xsl:comment>Failed to connect to db via driver/url connection</xsl:comment>
          <xsl:if test="$debug = 'true'">
            <xsl:copy-of select="sql:getError($connection)/ext-error"/>
          </xsl:if>
        </xsl:if>
      </xsl:otherwise>
    </xsl:choose>
          
          <xsl:variable name="table" select="sql:query($connection, $query)"/>
          <xsl:if test="not($table)">
               <xsl:message>Error in Query</xsl:message>
               <xsl:copy-of select="sql:getError($connection)/ext-error"/>
          </xsl:if>
          <page>
               
               <xsl:copy-of select="xalan:checkEnvironment()"/>
               
               <meta>
                    <cols>
                         <xsl:apply-templates select="$table/sql/metadata/column-header"/>
                    </cols>
               </meta>
               <rowset>
                    
                    <xsl:apply-templates select="$table/sql/row-set"/>
               </rowset>
          </page>
          <xsl:value-of select="sql:close($connection)"/>
     </xsl:template>
     <xsl:template match="row">
          <row>
               <xsl:apply-templates select="col"/>
          </row>
     </xsl:template>
     <xsl:template match="column-header">
          <col>
               <xsl:attribute name="type">
                    <xsl:value-of select="@column-typename"/>
               </xsl:attribute>
               <xsl:attribute name="display-name">
                    <xsl:call-template name="create-display-name"/>
               </xsl:attribute>
               <xsl:value-of select="@column-name"/>
          </col>
     </xsl:template>
     
     <xsl:template name="create-display-name">
          <xsl:variable name="col-name">
               <xsl:for-each select="str:tokenize(@column-name, '_')">
                    <xsl:value-of
                         select="concat(translate(substring(., 1, 1), $lowercase, $uppercase), translate(substring(.,2), $uppercase, $lowercase), ' ')"/>
               </xsl:for-each>
          </xsl:variable>
          <xsl:value-of select="substring($col-name, 1, string-length($col-name) - 1)"/>
     </xsl:template>
     
     <xsl:template match="col">
          <col>
               <xsl:attribute name="column-name"><xsl:value-of select="@column-name"/></xsl:attribute>
               <xsl:value-of select="."/>
          </col>
     </xsl:template>
</xsl:stylesheet>

XML Namespace and schemalocation property?

In many xml examples i see many nameschemas which even dont use in xml like in below example we have defined nameschemas as xsi,aop and one default
namespace. If we dont use them what the purpose of defining them.Did not attach the xml as its quite big.
Second question is :- Assume that we using this nameschemas..We usually defined the values of namechemas and schemalocation with some web address
like http://someAdddress//. What if we define them with some arbitrary value like ABC or something else. Will it make any differnce? Is there any
processing we do from these web addresses?
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:aop="http://www.springframework.org/schema/aop"
xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/
schema/beans/spring-beans-2.0.xsd http://www.springframework.org/schema/aop http://www.springframework.org/schema
/aop/spring-aop-2.0.xsd">

Take a look at these:
http://www.w3.org/TR/REC-xml-names/
http://www.w3.org/TR/xmlschema-1/
http://www.w3.org/TR/xmlschema-2/
Regards,
AK~

Parsing XML Namespace in as2

HI, I am attempting to parse some weather information from the Yahoo weather RSS feed.
This is a typical XML node;
<description>Yahoo! Weather for Palm Springs, CA</description>
I used the typical XML parsing code in as2;
var text1 = this.firstChild.childNodes[0].childNodes[1].firstChild.nodeValue;
txt1.text = text1;
I was doing pretty good until I reached a node that was formatted thus;
<yweather:forecast day="Mon" date="28 Sep 2009" low="74" high="103" text="Sunny" code="32" />
This text traced a value of undefined.
I have tried to research this and so far all I have been able to find out, is that this is a XML namespace and is very easily handled in as3. Unfortunately I have to use as2.
How do I parse out this information into a dyamic text fields?
Or failing that, where in the literature does adobe expalin how this is done?
Forrest

Hi,
Try this code:
var xmlname:XML = new XML();
xmlname.ignoreWhite = true;
xmlname.load("sample.xml");
xmlname.onLoad = function(sucess:Boolean){
var xNode = xmlname.firstChild;
var tday = xNode.childNodes[0].attributes.day;
var tdate = xNode.childNodes[0].attributes.date;
trace(tdate);

XML parser and XML processor

Hi,
I am trying to load the XML Parser and XSLT processor into the XDK that i have. Please can someone tell me how this is done. So far i keep hearing about classpath and .jar files. i have no idea what to do with these. Is there a manual which will tell me how to do this? Or can anyone explain to me?. Or can anyone tell me how to check if they are already there, the technican installed the software but does not know how to use it!, so i am very lost with this and am using it for my masters project.
Hope you can help.
Thanks

Hi,
I have checked the lib folder. xmlparsev2.jar is there. Is this the classpath? if not how do i get it to the classpath? and how do i do that?
Thanks for your help so far

XML Payload does not have namespace and prefix.

Hello
I have created a consumer business service which will be called from JDEdwards EOne, pulls data from database and send it to Fusion Middleware.
SO, I have created proxy using JAX-WS option. And suggested in oracle doc, I created proxy outside OMW and then copied it to my project. XML payload is getting generated without namespace and prefix. After some research, I modified package-info.java. Now, I am able to send the payload and if test it locally from Jdeveloper and take xml output using marshaller I can see it has namespace and prefix as well. BUt, when I run this from server it does not have namespace and prefix.
Please help.
Thanks
TK

Hi Naresh,
The "rejectedMessage" property is for 10G, I am not 100% sure about its implementation in 11G.
In 10G the faulted XML file moves to this location "Oracle_Home\bpel\domains\domain_name\jca\project_directory\rejectedMessages".
This property is used to move the files which are not valid XML or which are not schema compliant. For DB polling I don't think this property is used.
-Yatan

Namespace and prefix are not coming up in xml payload created from BSSV

Hello
I am facing this issue that when I am creating xml payload from BSSV, payload does not have namespace and no prefix. I googled on this and made code change in package-info. java file. Now, when I test BSSV locally from Jdeveloper xml gets created with namespace but when I run it from server, there's no namespace.
Does this file package-info.java gets deployed on server? is it ok to make change to it? If not, then what is the other way to resolve this issue?
Please suggest.
Thanks
TK

Hi Peter,
Thanks for the valuable input.
We have already implemented note 378648 i.e these all parameters are already there under sidadm user in DB node.
BR_OFS=1
BR_OFS_RESOURCE=< database_resource_name>
BR_OFS_CLUSTER=< cluster_name>
BR_OFS_USER=<user_name>
BR_OFS_DOMAIN=<domain>
BR_OFS_PWD=<password>
registry HKEY_LOCAL_MACHINE/Software/Oracle/HomeX ORA_<SID>_AUTOSTART is having value false.
Please guide what could be the other possible reason?
Regards
Praveen

BI Admin Tool and XSLT transformation for XML data source - How it works ?

Hello,
There is a possibility to import data from XML data source using BI Admin Tool.
In the import window we can point XSLT file. What is the purpose of that XSLT field?
Why I am asking ?
I thought it is smth like XSLT processor, but simply it doesnt work.
What I did:
- I pointed XML data source file
- I pointed XSLT transformation file
- Click OK, and still get the message that the XML file structure is not supported
After that I transformed that XML file with some desktop XSLT processor using the same XSLT file, and I tried to connect that file directly using BI Admin tool.Then it works. So it means that the transformation is ok.
So basically one question comes to my mind in that situation:
What is the purpose of XSLT field in BI Admin Tool when it comes to XML data source ?
(it doesnt look like XSLT processor)
Greetings
/Michal

Hi Mariano
Why you need to use XSLT for transforming XML file into ABAP table
Code is a part of some ABAP report. Looks like it is reading a file from file system and updating table after transformation
If you have requirement like you need to read XML file and then insert the data into a SAP table
You can use
File to RFC
File to Proxy scenario using SAP PI.
Please provide more inputs on requirement to help
Thanks
Gaurav

Examples related to XML and XSLT

Hello friends,
In relation to XML and XSLT
1. As I can transform an XML file using XSLT.
2. I view the XML file using XSLT
3. XSL and XSLT files are equal...?
Thanks for the support

http://docs.oracle.com/javaee/1.4/tutorial/doc/JAXPXSLT6.html

XML without namespace and prefix, modified package-info.java, JAX-WS option

Hello
I have created a consumer business service which will be called from JDEdwards EOne, pulls data from database and send it to Fusion Middleware.
SO, I have created proxy using JAX-WS option. And suggested in oracle doc, I created proxy outside OMW and then copied it to my project. XML payload is getting generated without namespace and prefix. After some research, I modified package-info.java. Now, I am able to send the payload and if test it locally from Jdeveloper and take xml output using marshaller I can see it has namespace and prefix as well. BUt, when I run this from server it does not have namespace and prefix.
Please help.
Thanks
TK

Just to clerify,
The common complex types are StatusInfo, IdcProperty and IdcPropertyList. I ahve 3 more WSDL's with the exact same entires for those 3.

Using XML extraction from Oracle and XSLT data transformation

Hi
How can transfer data ie: Using XML extraction from Oracle and XSLT data transformation with java application?
usually i use to do querying sql, getting data from table assinging to model class then send it to UI. how can i go for XML extraction form oracle?
thanks

Sorry, I don't understand what exactly you want to do. And I'm under the impression that you might not know exactly what you want to do as well. Could you explain a bit more detailed what you want to achieve?

[svn] 3663: Dita xml and xslt support for SkinStates

Revision: 3663
Author: [email protected]
Date: 2008-10-15 13:04:27 -0700 (Wed, 15 Oct 2008)
Log Message:
Dita xml and xslt support for SkinStates
Bugs: SDK-17166
QA: Yes
Doc: No
Tests: checkintests
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-17166
Modified Paths:
flex/sdk/trunk/asdoc/templates/class-parts.xslt
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/TopLevelClassesGenerator.ja va

http://docs.oracle.com/javaee/1.4/tutorial/doc/JAXPXSLT6.html

Xml namespace and xslt

Similar Messages

Maybe you are looking for