ABAP XML transformation problem

Hi all,
I am creating an XML based on a custom transformation I have made. The problem I have is that my variables type P decimals 2 are passed to the XML with just one decimal place, but I need two decimal places.
I was investigating and SAP documentation says that it should be passed with 2 decimal places according to the conversion, however it is not working in my case.
The only solution I found is making those variables type C, but I really want a solution that allows me keep my fields as type P.
Thanks in advance

Hi,
That's strange, it works well on my computer. I guess you should check SAP notes or contact SAP support.
Sandra

Similar Messages

XML Transformation Problem in JDeveloper 11.1.1.3.0

Friends,
I am trying to transform an XML using an XSL, by a Java program, which uses javax.xml.transform.Transformer.
I have a Java project which has the above program and I have a Web project created, where i have the java project's jar in the WEB-INF/lib. And, when i tried to access the same java program from inside the web project, I am getting the following error:
XML-22000: (Fatal Error) Error while parsing XSL file ({0}).
oracle.jbo.JboException: XML-22000: (Fatal Error) Error while parsing XSL file ({0}).
Code in ServiceAMImpl class:
TransformerFactory factory = TransformerFactory.newInstance();
template =
factory.newTemplates(new StreamSource(AMImpl.class.getClassLoader().getResourceAsStream("text.xsl")));
AMImpl.class.getClassLoader().getResourceAsStream("text.xsl") is returning NULL.
Please help in resolving this error.
Thanks much.

Hi,
I figured out the problem. The file was not in correct class path. Now it works fine.
Thanks everyone.

XML transformation problems - URGENT!!!!!

Hi,
I have a problem on writing data into XML files on Win NT/Tomcat platform from a servlet. This problem has been getting on my nerves for the past few weeks now. It was earlier giving a SecurityException: sealing violation error, when trying to write into the XML file using the Transformer object's transform method. What I need to do is, just read in data from the XML file first, do some processing and then dump in the results back in the same XML file.
I managed to get rid of the Sealing violation exception now, by downloading the xalan2 package and giving the reference of the new xalan.jar in the classpath. I am using the JAXP Transformer class's transform method to change the XML document. But, the problem now is that it is throwing a NoSuchMethodError exception on the line where the transform(source, result) method is coded.
This is the source code:
private void writeXMLData(Node n) throws IOException
     Transformer transformer;
     StreamResult streamresult;
     DOMSource domsource;
     TransformerFactory factory;
     factory= TransformerFactory.newInstance();
     try
     transformer = factory.newTransformer();
     domsource = new DOMSource(n);
transformer.transform(domsource, new javax.xml.transform.stream.StreamResult(new                FileOutputStream("d:\\tomcat\\webapps\\ROOT\\Orders.xml")));
     catch (Exception e)
          e.printStackTrace();
transformer = null;
factory=null;
domsource= null;
streamresult=null;
This is the error that is thrown:
java.lang.NoSuchMethodError: org.w3c.dom.Node: method getNamespaceURI()Ljava/lang/String; not found
     at org.apache.xpath.DOM2Helper.getNamespaceOfNode(DOM2Helper.java:348)
     at org.apache.xml.utils.TreeWalker.startNode(TreeWalker.java, Compiled Code)
     at org.apache.xml.utils.TreeWalker.traverse(TreeWalker.java, Compiled Code)
     at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java, Compiled Code)
     at test.TestOrderAdd_proto.writeXMLData(TestOrderAdd_proto.java:427)
     at test.TestOrderAdd_proto.doPost(TestOrderAdd_proto.java:228)
     at test.TestOrderAdd_proto.doGet(TestOrderAdd_proto.java:246)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:402)
     at org.apache.tomcat.core.Handler.service(Handler.java:287)
     at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372)
     at org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:797)
     at org.apache.tomcat.core.ContextManager.service(ContextManager.java:743)
     at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.java:213)
     at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java, Compiled Code)
     at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
     at java.lang.Thread.run(Thread.java:479)
The classpath settings are:
d:\jaxp-1.1\jaxp.jar;d:\xalan2\xalan-j_2_2_D9\bin\xalan.jar;d:\jaxp-1.1\crimson.jar (in that order)
Could anyone please help me out with this problem?
Thanks,
Jatin

I assume you're starting tomcat by using the tomcat.bat file. Keep in mind that this batch file adds every .jar file in tomcat's lib directory BEFORE your own classpath and it usually contains a parser.jar file, which might cause problems, it also contains a jaxp.jar.
If you want to switch to xerces, remove jaxp and crimson from your classpath and add xerces.jar to it (xerces contains jaxp). In the case of tomcat, you'd need to delete parser.jar and add xerces.jar to its lib dir.
Hope that helps.

XML Transformation Problem in JDeveloper 10.1.3

I am trying to transform an XML using an XSL, by a Java program, which uses javax.xml.transform.Transformer.
I have a Java project which has the above said program, where when i run the program, the xml transformation is done successfully.
But I have a Web project created, where i have the java project's jar in the WEB-INF/lib. And, when i tried to access the same java program from inside the web project, I am getting the following error:
XML-22000: (Fatal Error) Error while parsing XSL file (unknown protocol: c).
Please help in resolving this error.

This is from Metalink:
Cause
This is caused by a conflict between the Oracle XML parser installed by default in OC4J and the
Xerces parser that the application was developed with. Under 10.1.3 OC4J it is possible to tell OC4J not to use the default XML parser for the application at deployment time.
Solution
1. Undeploy the existing application using AS Console.
2. Start a new deployment of the application in AS Console. Click deploy
3. On the Deploy: Select Archive screen, browse to your deployment war file. Click Next
4. On the Deploy: Application Attributes give the application a name and click next
5. On the Deploy: Deployment Settings screen, click the pencil "Go To Task" Icon for the Configure Class Loading option.
6. Locate the shared library called "oracle.xml" (You may need to click "next 10" one or many times depending on the number of shared libraries you have) . For this row, UNCHECK the box for the column "IMPORT". Click OK
7. Click deploy, then test you application.

XML transformation -- abap

Hi Experts, I need help with this XSLT for call transformation. I have defined an internal table and intend to use it as a source for Call Tranformation. But I have Problems to defining my internal table to get the resut of the function transformation.(SAP 4.7)
In my case i have a xml with attibutes and i can't store these attibutes in internal table.
Hope to hear from any of u soon!
CMA
<--XSLT--
>
<xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:sap="http://www.sap.com/abapxml" version="1.0">
<xsl:template match="//Catalog">
    <asx:abap xmlns:asx="http://www.sap.com/abapxml">
      <asx:values>
        <CATALOG>
          
          <xsl:for-each select="EnTete">
            <ENTETE>
              <EMETTEUR>
                <xsl:value-of select="Emetteur"/>
              </EMETTEUR>
              <DATEPUBLICATION>
                <xsl:value-of select="DatePublication"/>
              </DATEPUBLICATION>
              
              <xsl:for-each select="Univers">
                <UNIVERS>
                  <LIBELLE>
                    <xsl:value-of select="@libelle"/>
                  </LIBELLE>
                  <OBJREF>
                    <xsl:value-of select="@objref"/>
                  </OBJREF>
                  <OBJID>
                    <xsl:value-of select="@objid"/>
                  </OBJID>
                  <EMETTEUR>
                     <xsl:value-of select="Emetteur"/>
                 </EMETTEUR>
                </UNIVERS>
              </xsl:for-each>
            </ENTETE>
          </xsl:for-each>
          
        </CATALOG>
      </asx:values>
    </asx:abap>
</xsl:template>
</xsl:transform>
<--XML--
>
<?xml version="1.0" encoding="UTF-8"?>
<asx:abap xmlns:asx="http://www.sap.com/abapxml">
<asx:values>
<Catalog>
     <EnTete>
          <Emetteur>UGAP</Emetteur>
          <DatePublication>27/06/2007 09:20:02</DatePublication>
              <Univers libelle="Nettoyage, hygine et entretien" objref="08" objid="374417o.bemp" >
                 <Emetteur>UGAP</Emetteur>
              </Univers>
           <Univers libelle="Nettoyage, hygine et entretien" objref="09" objid="374417o.bemp" >
                 <Emetteur>UGAP</Emetteur>
              </Univers>
</EnTete>
</Catalog>
</asx:values>
</asx:abap>
<--abap--
>
TYPES: BEGIN OF t_universs,
       libelle(35),
       objref(35),
       objid(35),
      boutique TYPE t_boutique,
       END OF t_universs.
TYPES: t_univers TYPE t_universs OCCURS 0.
               UNIVERS                 *
TYPES: BEGIN OF t_entetes,
            Emetteur(20),
            DatePublication(30),
            UNIVERS TYPE t_univers,
         END OF t_entetes.
*TYPES: t_entete TYPE t_entetes OCCURS 0.
DATA: it_data    TYPE STANDARD TABLE OF t_entetes,
      wa_data    TYPE t_entetes.
PARAMETER p_file(200) DEFAULT '/tmp/catalogue4.xml' LOWER CASE .
start-of-selection.
DATA: dsn(20) VALUE '/usr/catalogue2.xml',
      msg(100).
data : l_sysubrc like sy-subrc.
*OPEN DATASET p_file FOR INPUT MESSAGE msg
                IN TEXT MODE ENCODING DEFAULT.
OPEN DATASET p_file FOR INPUT IN BINARY MODE.
IF sy-subrc = 0.
CLEAR : gv_read_xml.
clear l_sysubrc.
READ DATASET p_file INTO gv_read_xml.
Transformation XML en ABAP-DATA
PERFORM check_xml USING gv_read_xml.
CLOSE DATASET p_file.
ENDIF.
*& Form check_xml
FORM check_xml USING p_xml TYPE string.
DATA: cx_runtime_error TYPE REF TO cx_xslt_runtime_error.
DATA: cx_format_error TYPE REF TO cx_xslt_format_error.
DATA: err_text TYPE string.
DATA: lt_xml TYPE STANDARD TABLE OF typ_xml,
      ls_xml TYPE typ_xml,
      source_xml TYPE string,
      lt_result_xml TYPE abap_trans_resbind_tab,
      ls_result_xml TYPE abap_trans_resbind.
TRY.
CALL TRANSFORMATION ZUGAP
SOURCE XML p_xml
RESULT CATALOG = it_data.
ENDTRY.
LOOP AT it_data INTO wa_data.
ENDLOOP.
i'm wonder if is it possible to get attribute from xml with abap function transformation...
Hope to hear from any of u soon!

Hi Marcelo,
Thanks a lot for your reply, your code is very usefull but my problem is located around the XSLT file.
With my progam (abap), I can't read the attibutes from a XML file correctly because the XSLT have not the suitable tags.
In my XML i have 2 rows of "Univers" and after use the function transformation from abap i can store only 1 rows in internal table   :
<Catalog>
     <EnTete>
          <Emetteur>UBB</Emetteur>
              <b><Univers libelle="Nettoyage, hygine et entretien" objref="08">
              </Univers>
              <Univers libelle="Nettoyage, hygine et entretien" objref="09">
              </Univers></b>
              </EnTete>
</Catalog>
XSLT :
<xsl:for-each select="EnTete">
            <ENTETE>
              <EMETTEUR>
                <xsl:value-of select="Emetteur"/>
              </EMETTEUR>
               <xsl:for-each select="Univers">
                <UNIVERS>
                  <UNIVERS1>
                    <LIBELLE> <xsl:value-of select="@libelle"/></LIBELLE>
                    <OBJREF> <xsl:value-of select="@objref"/> </OBJREF>
                  </UNIVERS1>
                </UNIVERS>
               </xsl:for-each>
            </ENTETE>
          </xsl:for-each>
My question is : How can i do to define attributes in XSLT to allow read them by a program abap ?
In my example, the program abap get only 1 attribute in my iternal table, what is the suitable syntax in the xslt to read all the attributes ?
Hope to hear from any of u soon!
Christophe.

File size problem when performing XML Transformation into Excel

Hi All,
We are performing XML Transformation in ABAP which can open in Excel and saving to common share. But the file size of excel is around 50MB. After opening the excel and save with diffrent name the file is getting compressed and its below 1MB. So what kind of settings does we need to make to the transformation code which will create the excel files with less memory/size??
<?sap.transform simple?>
<tt:transform xmlns:tt="http://www.sap.com/transformation-templates">
<tt:root name="AAAAAAA"/>
<tt:root name="BBBBBBBB"/>
<tt:root name="CCCCCCCC"/>
<tt:template>
<?mso-application progid="Excel.Sheet"?>
<Workbook xmlns="urn:schemas-microsoft-com:office:spreadsheet"
xmlns:o="urn:schemas-microsoft-com:office:office"
xmlns:x="urn:schemas-microsoft-com:office:excel"
xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882"
xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet"
xmlns:html="http://www.w3.org/TR/REC-html40">
   <ProtectObjects>True</ProtectObjects>
   <ProtectScenarios>True</ProtectScenarios>
</WorksheetOptions>
</Worksheet>
</Workbook>
</tt:template>
</tt:transform>
<DocumentProperties xmlns="urn:schemas-microsoft-com:office:office">
</DocumentProperties>
<CustomDocumentProperties xmlns="urn:schemas-microsoft-com:office:office">
<ContentTypeId dt:dt="string">0x01010049B4763FE606154C9C9BC639FE7EE179</ContentTypeId>
</CustomDocumentProperties>
<OfficeDocumentSettings xmlns="urn:schemas-microsoft-com:office:office">
<Colors>
   <Color>
    <Index>0</Index>
    <RGB>#FF0000</RGB>
   </Color>
   <Color>
    <Index>1</Index>
    <RGB>#FFE4B5</RGB>
   </Color>
   <Color>
    <Index>2</Index>
    <RGB>#FFF8DC</RGB>
   </Color>
   <Color>
    <Index>3</Index>
    <RGB>#000000</RGB>
   </Color>
</Colors>
</OfficeDocumentSettings>
<ExcelWorkbook xmlns="urn:schemas-microsoft-com:office:excel">
<WindowHeight>7305</WindowHeight>
<WindowWidth>11340</WindowWidth>
<WindowTopX>0</WindowTopX>
<WindowTopY>0</WindowTopY>
<TabRatio>334</TabRatio>
<ProtectStructure>True</ProtectStructure>
<ProtectWindows>False</ProtectWindows>
</ExcelWorkbook>
</DocumentProperties>
<CustomDocumentProperties xmlns="urn:schemas-microsoft-com:office:office">
<ContentTypeId dt:dt="string">0x01010049B4763FE606154C9C9BC639FE7EE179</ContentTypeId>
</CustomDocumentProperties>
<OfficeDocumentSettings xmlns="urn:schemas-microsoft-com:office:office">

Hi Raghu,
have a look at the XLSX file generated by Excel, you'll see that it's simply a zipped file. So you can't do it with a transformation, but you need CL_ABAP_ZIP class. I advise you to look at the abap2xslx project ABAP code (currently 3.0) to see how it works.
Best regards,
Sandra

Styling XML with XSLT Problem with javax.xml.transform???

I have been trying to make a transformation and seem to be having a problem in that javax.xml.transform can not be found while using jdk1.3....If I use jdk1.4, there is no problem....
Does anyone know how I can get things to work using jdk1.3???
(Description of what I am doing...1) Building XML Source 2) Setting up the XSLT File 3) Building Source Object 4) Build Result Object 5) Transforming the Data.....MY RESULT SHOULD BE AN HTML PAGE)
I have tried putting xerces.jar and xalan.jar in my CLASSPATH....but this still doesn't work....onyl thing that has worked is using jdk1.4 as my JAVA_HOME....
PLEASE HELP!!!!

PLEASE HELP....your advice here would be greatly appreciated.....

Problem with JBuilder and javax.xml.transform package

Hi,
My JBuilder 7 can not find javax.xml.transform package. i use javax.xml.parsers package but i can not access to javax.xml.transform. is there a problem or something necessary to do to access that?
Best Wishes - WiseWarrior

Hey WiseWarrior,
your problem is directly related to your jar file in run time. The xml parser jar which you are using to perform transfor is not having the appropriate classes, take the latest version of xalan it has transform package and put it into your class path, it will work.
CheerS!!
Sandeep Raikwar

XML Transformation error (ABAP -- XML)

Hi,
I'm getting the foll. error while doing a XML Transformation, Can anyone help me in this regard..
<FIN_WT>56.0</FIN_WT>
<FIN_WT_UNIT>KG</FIN_WT_UNIT>
<ZZQMNUM />
<ZZHOLD />
<ZZDUMATNR
The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.
The following tags were not closed: asx:abap, asx:values, OUTPUT, item. Error processing resource 'file:///C:/Documents and...
> />
<PSP_NR>U5/0626-HT-193-1-36-344</PSP_NR>
<ZZCRTNAME>ALFI</ZZCRTNAME>
<ZZAPPNAME>ALFI</ZZAPPNAME>
Regards
Jiku

are you trying to transform XML to itab?
is the xml well formed one - you can check this by running the xml file in webbrowser, if it doesnt display, then it means the xml is not well formed.
Regards
Raja

Java transform problem - resulting XML has wrong namespace on imported Node

I use Document.importNode(Node, String) to import a node from one document into another document. I want to preserve the namespace of the imported node. This works ok if the imported node specifies xmlns, even xmlns="". But if the imported node does not specify a namespace, I would expect the resulting serialized XML to have xmlns="". However, this is not the case. I use javax.xml.transform.Transformer when I serialize the XML. After the transform, the imported node has the namespace of the document it is imported into, which we do not want. So how do I get the imported node to serialize out with xmlns="", even if it's not specified in the source document? I am using javax.xml.transform.* and javax.xml.parsers.DocumentBuilder from Java 1.4.2.
Example of XML that node is imported into (imported node replaces PayloadPlaceHolder):
<?xml version="1.0" encoding="UTF-8"?>
<Envelope envelopeVersion="0.0.0" classificationLevel="Unclassified" xmlns="http://disa.gcss.mil/XMLGateway/Envelope">
<Header>
<UID>GM0000001</UID>
<DateTime>2006-12-05T16:11:50Z</DateTime>
</Header>
<Status reason="FAILED" lastTransactionID="9999999999" inReplyTo="ZZZ9999999999">
<LastMessageUID>ZZZ9999999999</LastMessageUID>
</Status>
<Payload>
<PayloadPlaceHolder>
</PayloadPlaceHolder>
</Payload>]
</Envelope>
Example of XML with null namespace, test_segment is imported node:
<?xml version="1.0" encoding="UTF-8"?>
<test_segment>
<name>test</name>
</test_segment>
Example of result XML with imported node (test_segment):
<?xml version="1.0" encoding="UTF-8"?>
<Envelope classificationLevel="Unclassified" envelopeVersion="0.0.0" xmlns="http://disa.gcss.mil/XMLGateway/Envelope">
<Header>
<UID>GM0000001</UID>
<DateTime>2006-12-05T16:11:50Z</DateTime>
</Header>
<Status inReplyTo="ZZZ9999999999" lastTransactionID="9999999999" reason="FAILED">
<LastMessageUID>ZZZ9999999999</LastMessageUID>
</Status>
<Payload>
<test_segment>
<name>test</name>
</test_segment>
</Payload>
</Envelope>
Here is the code to build the documents and transform the XML:
     Document document = null;
Document dataBlockDoc = null;
ByteArrayInputStream inStream = new ByteArrayInputStream
(StringUtils.getBytes(xml.toString()));
try {
DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
dbf.setNamespaceAware( true );
DocumentBuilder parser = dbf.newDocumentBuilder();
document =
parser.parse(
new InputSource(inStream ) );
if (dataBlock != null) {
inStream = new ByteArrayInputStream(StringUtils.getBytes(dataBlock));
dataBlockDoc = parser.parse(
new InputSource(inStream ) );
Element root = document.getDocumentElement();
Element payload = null;
NodeList children = root.getChildNodes();
//get Payload child from envelope document
for (int i = 0; i < children.getLength(); i++) {
if (children.item(i).getNodeName().equals("Payload")) {
payload = (Element)children.item(i);
break;
//get the PayloadPlaceHolder
Element payloadPlaceHolderElement = null;
children = payload.getChildNodes();
for (int i = 0; i < children.getLength(); i++) {
if (children.item(i).getNodeName().equals("PayloadPlaceHolder")) {
payloadPlaceHolderElement = (Element)children.item(i);
break;
Node newPayload = null;
if (dataBlockDoc != null) {
Element dataBlockElement = dataBlockDoc.getDocumentElement();
//make new Payload element to replace old (empty) Payload
newPayload = document.importNode((Node) dataBlockElement, true);
payload.replaceChild(newPayload, payloadPlaceHolderElement);
else
payload.removeChild(payloadPlaceHolderElement);
TransformerFactory tf = TransformerFactory.newInstance();
Transformer nullTransform = tf.newTransformer();
ByteArrayOutputStream oStream = new ByteArrayOutputStream();
nullTransform.transform(                    new DOMSource( document ),
     new StreamResult( oStream ) );
xml = new StringBuffer(oStream.toString());
Thanks in advance.

It appears that the problem is that the DOM serializer implementation in JDK 1.4 is not properly handling namespaces. Does anyone know of a workaround or alternate serializers we could use to serialize a DOM tree? I also need it to work with XSLT.
Thanks.

Problem with return of javax.xml.transform.Source impl from webService

I have a web services that needs to return an XML string to the calling client. If I return the XML as a String object it gets deserialized twice and the end result is no longer XML. My research indicates that I can return an implementation of javax.xml.transform.Source and this will cause SOAP to attach the XML string to the message rather than embed it (protecting it from deserialization). The following is the effective part of my method:
public Source[] consumeTextMessage(String id) throws RemoteException {
try {
MessageConsumer mc = new MessageConsumer();
String[] messages = mc.consumeTextMessage(id);
StreamSource[] sources = new StreamSource[messages.length];
for(int i = 0; i < messages.length; i++) {
sources[ i ] = new StreamSource();
return sources;
} catch(RemoteException e) {
throw e;
note: the mc.consumeTextMessage(id) call works correctly and I know that I'm not putting anything in the StreamSource objects in the loop to build the array of StreamSource objects - just trying to get SOMETHING to work
so this deploys without problem, but when I try to get a wsdl for the webservice i get a Server 500 error; the log says this:
javax.servlet.ServletException: WSDL Generation exception: java.lang.Exception javax.xml.transform.Source is an abstract class: cannot be instanciated
ok.... if I change the method return type to a concrete class (StreamSource[]), redeploy and try to get a wsdl, I get this absolutely crazy error:
javax.servlet.ServletException: WSDL Generation exception: java.lang.Exception java.io.Reader is an abstract class: cannot be instanciated
I have NO clue why it thinks it needs a Reader.
If I change the method return type to String[] (and make the various adjustments to the method) then it deploys ok and gives me a good WSDL (though it still doesn't work because the Strings are deserialized twice so this isn't a viable solution but it does show that my webservice config is correct).
So... bottom line seems to be that the webService "engine" of 10g AS doesn't like Source or StreamSource.....
Any ideas what I can do??

Funny story here: trying to deploy a different webserivce all together and got the same error message; thought I remembered seeing it before but wasn't sure; did a google search on it and lo and behold came across my first posting in this thread.... crazy.
Anyway, I have discovered something that answers some of the questions I had in my first post: It seems that the argument types used in a webservice signature MUST be CONCRETE classes (and I would think primitives would work too though I don't remember trying them) - they can not be Interfaces or abstract classes. Probably if I read the webservices spec it would tell me that.
So the error I was getting before was because Source was not a concrete class, and presumably the second error was caused by some signature somewhere along the line using the Reader abstract class.
Fun stuff.

XSL problem with javax.xml.transform.sax.SAXTransformerFactory

Dear sirs,
I use SAXTransformerFactory in order to transform a Hashtable to SAX Event and apply a XSL.
I try this code with the lastest version of apache parser.
It run well.
But, I put this software to WEBLOGIC 6.2 server and no run.
this check is true:
          if (transFact.getFeature(javax.xml.transform.sax.SAXTransformerFactory.FEATURE)&&transFact.getFeature(javax.xml.transform.sax.SAXSource.FEATURE))
Some one can help me.
Thank in avance
The code:
java.io.ByteArrayOutputStream bout = new java.io.ByteArrayOutputStream();
          com.cajarural.xml.HashtableParser parser = new com.cajarural.xml.HashtableParser(hashtable);
          // Codigo para el TansformerHandler
          // set the destination for the XSLT transformation
               javax.xml.transform.TransformerFactory transFact = javax.xml.transform.TransformerFactory.newInstance();
               if (transFact.getFeature(javax.xml.transform.sax.SAXTransformerFactory.FEATURE)&&transFact.getFeature(javax.xml.transform.sax.SAXSource.FEATURE))
javax.xml.transform.sax.SAXTransformerFactory saxTransFact = (javax.xml.transform.sax.SAXTransformerFactory) transFact;
javax.xml.transform.sax.TransformerHandler transHand = saxTransFact.newTransformerHandler(templates);
transHand.setResult(new javax.xml.transform.stream.StreamResult(bout));
parser.setContentHandler(transHand);
// attach the XSLT processor to the           parser.parse();
          return new String(bout.toByteArray());

put Xalan in your war file then try using this kind of commands:     System.setProperty("org.xml.sax.parser", "org.apache.xerces.parsers.SAXParser");
System.setProperty("javax.xml.parsers.SAXParserFactory", "org.apache.xerces.jaxp.SAXParserFactoryImpl");
System.setProperty("javax.xml.parsers.DocumentBuilderFactory", "org.apache.xerces.jaxp.DocumentBuilderFactoryImpl");
System.setProperty("javax.xml.transform.TransformerFactory", "org.apache.xalan.processor.TransformerFactoryImpl");This tells JAXP what implementations it should use without even asking your administrator to modify the WebLogic setup...
It's what I've done with the WLS7.0 server I am using ;-)

Error in ABAP XSLT transformation

Hi,
Im trying to upload some data from XML to abap. But Im getting an error while transforming xml data to internal table.
Here are the details.
XML:
<?xml version="1.0" encoding="ISO-8859-1" ?>

<?xml-stylesheet type="text/xsl" href="ABAP1.xsl"?>
<conceptRevDecisionXml>
<projectInfo>
<projectId>P000755</projectId>
<stage>CON</stage>
<country>Ethiopia</country>
<region>AFRICA</region>
<teamleader>Priya Agarwal</teamleader>
<teamleaderfirstname>Priya</teamleaderfirstname>
<teamleaderlastname>Agarwal</teamleaderlastname>
<actionType>X</actionType>
</projectInfo>
</conceptRevDecisionXml>
XSLT: Transformation
<xsl:transform version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:sapxsl="http://www.sap.com/sapxsl"
>
<xsl:strip-space elements="*"></xsl:strip-space>
<xsl:template match="/">
    <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
      <asx:values>
        <PROJID>
          <xsl:apply-templates select="//conceptRevDecisionXml"></xsl:apply-templates>
        </PROJID>
      </asx:values>
    </asx:abap>
</xsl:template>
<xsl:template match="conceptRevDecisionXml">
      <xsl:for-each select="projectInfo">
       <xsl:value-of select="projectId"></xsl:value-of>
       <xsl:value-of select="stage"></xsl:value-of>
       <xsl:value-of select="country "></xsl:value-of>
       <xsl:value-of select="region"></xsl:value-of>
       <xsl:value-of select="teamleader"></xsl:value-of>
       <xsl:value-of select="teamleaderfirstname"></xsl:value-of>
       <xsl:value-of select="teamleaderlastname"></xsl:value-of>
        <xsl:value-of select="actionType"></xsl:value-of>
        </xsl:for-each>
    </xsl:template>
</xsl:transform>
Once I run the program...Im getting an error saying...ABAP XML Formatting error in XML node..
Im new to ABAP-XML parsing..Pls help me where Im going wrong..
Thanks in advance.
Regards,
Priya

Hi Priya,
you can try with the below,
1) Create a local ITAB with the structure of the XML,
TYPES: BEGIN OF t_data,
        projectid           TYPE char30,
        stage               TYPE char30,
        country             TYPE char30,
        region              TYPE char30,
        teamleader          TYPE char30,
        teamleaderfirstname TYPE char30,
        teamleaderlastname TYPE char30,
        actiontype          TYPE char30,
       END OF t_data.
2) Create an XSLT prog in "STRANS" with the below code,
<xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:sap="http://www.sap.com/sapxsl" version="1.0">
<xsl:strip-space elements="*"/>
<xsl:template match="/">
<asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
<asx:values>
<L_DATA>
<xsl:apply-templates select="//projectInfo"/>
</L_DATA>
</asx:values>
</asx:abap>
</xsl:template>
<xsl:template match="projectInfo">
<conceptRevDecisionXml>
<PROJECTID>
<xsl:value-of select="projectId"/>
</PROJECTID>
<STAGE>
<xsl:value-of select="stage"/>
</STAGE>
<COUNTRY>
<xsl:value-of select="country"/>
</COUNTRY>
<REGION>
<xsl:value-of select="region"/>
</REGION>
<TEAMLEADER>
<xsl:value-of select="teamleader"/>
</TEAMLEADER>
<TEAMLEADERFIRSTNAME>
<xsl:value-of select="teamleaderfirstname"/>
</TEAMLEADERFIRSTNAME>
<TEAMLEADERLASTNAME>
<xsl:value-of select="teamleaderlastname"/>
</TEAMLEADERLASTNAME>
<ACTIONTYPE>
<xsl:value-of select="actionType"/>
</ACTIONTYPE>
</conceptRevDecisionXml>
</xsl:template>
</xsl:transform>
3) Call the transformation as shown below,
CALL TRANSFORMATION zxslt_project ---> "Name of the XSLT prog created above
SOURCE XML l_xml_str                           ---> Source XML string
RESULT l_data = l_data.                          ---> ITAB as in step 1 above
Regards,
Chen

Fatal Error and NullPointerException in Oracle XML Transformer

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

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

Create XML transformation in SAP R/3 4.7

Hi Experts,
Kindly let me know the transaction for creating xml transformation in sap r/3 4.7, if there is any.
Though i could not find anything through tstc or se93.
Is there any other way of creating xml transformation in r/3 4.7. There is a tcode STRANS in ecc6.0 but not in 4.7.
Also, please help me resolving this issue of converting abap data to xml file: -
is the following xml structure possible with transformation or by any other method.
<Process_Order>
     <item>
               <PO Number> PO123334 </PO Number>
               <Header_mat> Mat123 </Header_mat>
               <BOM>
                      <PDLabels>
                              <PDLabel>
                                     <PCode>P123456</PCode>
                                     <Batch>123ABC</Batch>
                                     <Quantity>6000</Quantity>
                                     <PDDCode>1234567890</PDDCode>
                             </PDLabel>
                             <PDLabel>
                                    <PCode>P234567</PCode>
                                    <Batch>567DEF</Batch>
                                    <Quantity>6000</Quantity>
                                    <PDDCode></PDDCode>
                             </PDLabel>
                    </PDLabels>
                   <PDCartons>
                            <PDCarton>
                                   <PCode>P556677</PCode>
                                   <Batch>589GFT</Batch>
                                   <Quantity>1200</Quantity>
                                   <PDDCode></PDDCode>
                            </PDCarton>
                  </PDCartons>
             </BOM>
    </item>
     <item>
               <PO Number> PO123334 </PO Number>
               <Header_mat> Mat123 </Header_mat>
               <BOM>
                      <PDLabels>
                              <PDLabel>
                                     <PCode>P123456</PCode>
                                     <Batch>123ABC</Batch>
                                     <Quantity>6000</Quantity>
                                     <PDDCode>1234567890</PDDCode>
                             </PDLabel>
                             <PDLabel>
                                    <PCode>P234567</PCode>
                                    <Batch>567DEF</Batch>
                                    <Quantity>6000</Quantity>
                                    <PDDCode></PDDCode>
                             </PDLabel>
                    </PDLabels>
                   <PDCartons>
                            <PDCarton>
                                   <PCode>P556677</PCode>
                                   <Batch>589GFT</Batch>
                                   <Quantity>1200</Quantity>
                                   <PDDCode></PDDCode>
                            </PDCarton>
                  </PDCartons>
             </BOM>
    </item>
</Process_Order>
What i mean to ask is, is the hierarchy to this structural level is attainable using either transfomation or any other alternative.
Thanks a lot in advance !
Shreya

oops the message structure has gone bad ........
What i meant was : --
<Process_Order>
<item>
               <PO Number> PO123334 </PO Number>
               <Header_mat> Mat123 </Header_mat>
               <BOM>
                      <PDLabels>
                              <PDLabel>
                                     <PCode>P123456</PCode>
                                     <Batch>123ABC</Batch>
                                     <Quantity>6000</Quantity>
                                     <PDDCode>1234567890</PDDCode>
                             </PDLabel>
                             <PDLabel>
                                    <PCode>P234567</PCode>
                                    <Batch>567DEF</Batch>
                                    <Quantity>6000</Quantity>
                                    <PDDCode></PDDCode>
                             </PDLabel>
                    </PDLabels>
                   <PDCartons>
                            <PDCarton>
                                   <PCode>P556677</PCode>
                                   <Batch>589GFT</Batch>
                                   <Quantity>1200</Quantity>
                                   <PDDCode></PDDCode>
                            </PDCarton>
                  </PDCartons>
             </BOM>
    </item>
</Process_Order>

ABAP XML transformation problem

Similar Messages

Maybe you are looking for