XSLT 2.0 processor

It would be helpful to be able to choose between XSLT 1.0 and 2.0 when exporting XML with an XSLT stylesheet.
Related requests:
-- Ability to select an external XSLT processor on XML export.
-- Ability to pass parameter values to the processor on XML export.
SB

>
I want to use SaxonHE9.4.0.3 processor
>
Michael Kay provides extensive Installation instructions for all of his products. They are included in the documentation download.
Here is just a small part of what was provided for the version I use
>
Installation of Saxon simply involves unzipping the supplied download file into a suitable directory. The procedure is the same for the Standard product and the Schema-Aware product. The two products can co-exist in the same directory or in different directories.
One of the files that will be created in this directory is the principal JAR file. This is saxon8.jar in the case of Saxon-B, saxon8sa.jar in the case of Saxon-SA. There are additional JAR files to support optional features including the JDOM interface and the SQL interface. When running Saxon, the principal JAR file should be on the class path. The class path is normally represented by an environment variable named CLASSPATH: see your Java documentation for details. Note that the JAR file itself (not the directory that contains it) should be named on the class path.

Similar Messages

How to use another XSLT processor

Hello all,
Recently, I do need to use XSLT 2.0 processor, but how to install it to the JDK? Please give the detailed steps. And how to use it, just import the package? How to avoid the program to the old processor, because I doubt probably the old processor is part of the JDK. And how does this change impact to the java web service? And how do I change the web service about this change?
Thank you in advance.

>
I want to use SaxonHE9.4.0.3 processor
>
Michael Kay provides extensive Installation instructions for all of his products. They are included in the documentation download.
Here is just a small part of what was provided for the version I use
>
Installation of Saxon simply involves unzipping the supplied download file into a suitable directory. The procedure is the same for the Standard product and the Schema-Aware product. The two products can co-exist in the same directory or in different directories.
One of the files that will be created in this directory is the principal JAR file. This is saxon8.jar in the case of Saxon-B, saxon8sa.jar in the case of Saxon-SA. There are additional JAR files to support optional features including the JDOM interface and the SQL interface. When running Saxon, the principal JAR file should be on the class path. The class path is normally represented by an environment variable named CLASSPATH: see your Java documentation for details. Note that the JAR file itself (not the directory that contains it) should be named on the class path.

** How to use XSLT Stylesheet Ver 2.0 functions in XI 7.0?

Hi friends,
There are numerous built-in functions in SALT ver 2.0. Functions like upper-case, index-of, etc. They are very useful when use XSLT Mapping. But, unfortunately we are not able to use this functions in XSLT Mapping in XI. i.e XI throws an error like 'Transformation Configuration Error Occured'.
Friends your experience, kindly share your idea how do we to do in XSLT? Is any other alternate way there ?
Thanking you.
Yours friendly,
Jeg P.

You could of course try to import your own Java XSLT 2.0 processor in a .jar file and in the same or another .jar, you could import the .xslt files.
Regards,
Henrique.

How to create xml file from original

I have this complicated xml and I want to search through it and make a new xml with only element I find that match. what is the best way to do this? the file
is about 6mb and I want to read the whole file easily..should i load to database table and create a file from table? I have found issues reading the file..
- <ArrayOfJobClass xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
- <JobClass>
- <Triggers>
- <TriggerClass>
<ExpireActionType>Delete</ExpireActionType>
<ExpireType>DateTime</ExpireType>
<TriggerType>TimeType</TriggerType>
- <TTime>
<TimeTriggerType>Custom</TimeTriggerType>
<IntervalType>Daily</IntervalType>
<SpecificType>Days</SpecificType>
<FirstLastType>First</FirstLastType>
<IntervalValue>1</IntervalValue>
<FirstLastWeekDay>Monday</FirstLastWeekDay>
<InitDate>2009-05-04T14:17:05.40625-07:00</InitDate>
- <IntervalDays>
<boolean>false</boolean>
<boolean>false</boolean>
<boolean>false</boolean>
<boolean>false</boolean>
<boolean>false</boolean>
<boolean>false</boolean>
<boolean>false</boolean>
<boolean>false</boolean>
<boolean>false</boolean>
<boolean>false</boolean>
<boolean>false</boolean>
<boolean>false</boolean>
<boolean>false</boolean>
<boolean>false</boolean>
<boolean>false</boolean>
<boolean>false</boolean>
<boolean>false</boolean>
<boolean>false</boolean>
<boolean>false</boolean>

You can load it in the database in an XMLType table (Object-Relational or Binary XML storage), use XQuery on the XML content and then write back the result to a file.
Or, you might just use an external processor (XSLT or XQuery).
If you want to stay in the Oracle world, you can use :
- For XSLT : $ORACLE_HOME/bin/oraxsl (it's a wrapper for the java XSLT engine)
- For XQuery : the java XQuery API
Personally, I sometimes use the Saxon XSLT and XQuery processor, quite efficient.
Here's a simplistic example with oraxsl utility :
emp.xml
<?xml version="1.0" encoding="UTF-8"?>
<emps>
<emp id="7369">
 <name>SMITH</name>
 <job>CLERK</job>
 <salary>800</salary>
</emp>
<emp id="7499">
 <name>ALLEN</name>
 <job>SALESMAN</job>
 <salary>1600</salary>
</emp>
<emp id="7521">
 <name>WARD</name>
 <job>SALESMAN</job>
 <salary>1250</salary>
</emp>
<emp id="7566">
 <name>JONES</name>
 <job>MANAGER</job>
 <salary>2975</salary>
</emp>
<emp id="7654">
 <name>MARTIN</name>
 <job>SALESMAN</job>
 <salary>1250</salary>
</emp>
</emps>
emp.xsl
<?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"/>
<xsl:template match="text()"/>
<xsl:template match="emps/emp[job='SALESMAN']">
<xsl:copy-of select="."/>
</xsl:template>
</xsl:stylesheet>Applying the transformation to search and extract all "salesmen" :
D:\ORACLE\test>%ORACLE_HOME%\bin\oraxsl emp.xml emp.xsl result.xml
D:\ORACLE\test>type result.xml
<?xml version = '1.0' encoding = 'UTF-8'?>
<emp id="7499">
 <name>ALLEN</name>
 <job>SALESMAN</job>
 <salary>1600</salary>
</emp><emp id="7521">
 <name>WARD</name>
 <job>SALESMAN</job>
 <salary>1250</salary>
</emp><emp id="7654">
 <name>MARTIN</name>
 <job>SALESMAN</job>
 <salary>1250</salary>
</emp>

XSL 2.0 In Java (Eclipse IDE 3.2.2)

Hi....
How to Configure XSL 2.0 In Eclipse 3.2.2...
The Version XSL 1.0 is working properly. But When I add XSL 2.0 Elements in code it doesn't process the output.
Pls help me.....
Thanks in advance.....
Vinoop.

Well, first you will need to download an XSLT 2.0 processor and put it in your classpath. Then you will need to make the appropriate configuration changes to make Java use that processor and not the built-in XSLT 1.0 processor.

How to use correctly StyleSheet CSS In RAP

Hi all,
I use Kepler version and I would like to introduce in my application the use of Style-Sheet CSS for the RAP ui.
Could someone explain or indicate to me basic resources from which to start?
I searched something in forum and toturial section but without great success.
Thanks in advance for any help, suggestion and explanation

You could of course try to import your own Java XSLT 2.0 processor in a .jar file and in the same or another .jar, you could import the .xslt files.
Regards,
Henrique.

How can I make my XSLT processor accept html code ?

In my applications the Oracle xslt processor wont accept simple HTML tags within an XML source while transforming the source into HTML. Both processors either will throw parser exceptions or ignore the HTML code in the XML source completely, though output-escaping is explicitly enabled.
In detail, I want to transform an XML source like this...
<element>
Hello, this is a XML text source mingled with htmlTM
</element>
... with an XSL Stylesheet like this...
<xsl:stylesheet>
<xsl:output method=html cdata-sections=element/>
<xsl:template match=element>
<html>
<body>
<xsl:value-of select=. output-escaping=yes/>
</body>
</html>
</xsl:template>
</xsl:stylesheet>
... which should result in a HTML code like this ...
<html>
<body>
Hello, this is a XML text source mingled with htmlTM
</body>
</html>
The result, however, is always like this:
<html>
<body>
Hello, this is a XML text source mingled with htmlTM
</body>
</html>
This means that the additional HTML tags inside the XML source have been completely ignored by the XSLT processor though I enabled the output-escaping.
If anybody should think now that mingling HTML with XML text is stupid because I could also format the result with the XSL Stylesheet itself, he might be right, of course, but: I cant avoid this because in my application the XML source results from a users web form entry. The user working with the form must be able to decide whether he wants to include HTML in his text or not. In any case, any HTML code he enters should just be transported WITHOUT ANY CHANGES to the resulting HTML page, not omitted without comments! It seems quite simple to me, but the XSLT processor doesnt want to agree with me in this point :-(
So, once again in brief: Is there any possibility to tell my XSLT processor not to parse, transform or manipulate HTML tags, but to transport them unchanged to the output ?
After weeks of research any helping sign would be a great relief...
Many thanks in advance.

I don't understand the answer, can you please expand. I am trying to do a similar thing by creating an output buffer,
assemble a mix of text and html tags and then output this buffer later. All of the html tags are skipped or re-escaped in the final html:
In this example I want to print the IPRCROP, then add an html break ( ).
Example 1. Use xsl:text with escape = yes
<xsl:variable name="buffy">
<xsl:for-each select="documents/document">
<xsl:value-of select="IPRCROP"/>
<xsl:text disable-output-escaping="yes"> </xsl:text>
</xsl:for-each>
</xsl:variable>
<xsl:value-of select="$buffy"/>
In this case the and end up re-escaped in the output html as #60 etc. so they appear literally as
ALFALFA BARLEY 
and in source as: ALFALFA BARLEY
Example 2, try as pure text, it just skips the altogether
<xsl:variable name="buffy">
<xsl:for-each select="documents/document">
<xsl:value-of select="IPRCROP"/>
<xsl:text> </xsl:text>
</xsl:for-each>
</xsl:variable>
<xsl:value-of select="$buffy"/>
output = ALFALFABARLEY

How to use xsl document() function with LiveCycle XSLT processor

Hello,
I would like to use LiveCycle XSLT processor to merge xml documents by using the xsl document() function.
However, I have not, yet, found clear reference information on the specifics of how to accomplish in LC. For instance if you have
a transformation that does merging using a standalone xml editor (such as Oxygen), than what is required to accomplish the same
using the LiveCycle XSLT service. How do you specify the URI of the XML document that is specified as an input in the xsl document() function. Your insight is appreciated. Regards

Hello Steve,
I checked the reference that you cited (XSLT Transformation). The reference omits discussing how to use xlst document() function within a stylesheet. I think that probably means that feature of xslt technology is not directly available through LiveCycle. When I find a workaround, I'll post an update...for the user community that might encounter the same issue. Thank you for your response and insight. Regards, jb1809

Plugging XSLT / XML processors into Business Connector 4.7

Hi,
I need to use Xalan 2.6.0 and the associated XML parsers
in the Business Connector.
Does anyone know whether any built-in services or
SAP Adapter services would be negatively impacted by
this change? I have found nothing in the documentation.
(Among the reasons I need to do this are that the
processors in package com.inqmy.lib.jaxp do not seem to
be JAXP 1.2 compliant. Also, they neither respect the
encoding-attribute of <xsl:output>, nor allow to override
it from the outside. When generating HTML, this has
created problems for some clients).
In order to use Xalan/Xerces, one needs to set the
variable PREPENDCLASSES in server.bat to contain
the Xalan jars, and change the value of the configuration
variable watt.xslt.jaxp.properties in the server.cnf file.
The value of this variable is the name of a file in normal
Java properties syntax, which contains values for the
relevant System properties:
javax.xml.transform.TransformerFactory
javax.xml.parsers.DocumentBuilderFactory
javax.xml.parsers.SAXParserFactory
I'm using BC 4.7 SR2, Core Fix 2, JDK 1.3.1_09 under WinXP
At first glance everything seems to work fine (I can
still use recordToDocument), but I'd like to be sure.
And what about BC 4.6?
-- Sebastian Millies
IDS Scheer AG

Check out this weblog series for starters: /people/tobias.trapp/blog
Then I would suggest you post your question to the ABAP forum.

Using the XSLT processor for non-workbench XSLT

Hi there,
is it possible to use the built-in XSLT processor for arbitrary XSLT transformations which aren't checked in in the ABAP workbench but instead given as a runtime object (string or iXML)?
Instead of the built-in command CALL TRANSFORMATION which according to the doc is restricted to workbench transformations, I am looking for an option like this:
data: lo_transformation type ref to if_ixml_document,
 lo_source type ref to if_ixml_document,
 lo_target type ref to if_ixml_focument.
* I get lo_transformation and lo_source from somewhere out there
try.
 lo_target ?= cl_some_fine_class_which_i_am_looking_for=>transform(
 io_source = lo_source
 io_transformation = lo_transformation ).
catch cx_xslt_runtime_error.
endtry.
Does anybody know such a feature?
For a background about this problem - in German language - see my blog
http://ruediger-plantiko.blogspot.com/2007/08/xslt-in-bsp-anwendungen-und-in-abap.html
Thanks and Regards,
Rüdiger

Dear Rashid,
thanks - this is the answer! I wonder why I didn't find this class one year ago. A little test prog shows that it works fine and even performant (about 0.5 millisec for creating the new dynamic XSLT program with the method set_source_stream( ) ). For usage in web apps, it would be nice to know whether the temporary program remains available in the application servers' buffer after end of process. I can't check this, since this is performed on the C/C++ level, and SE30 doesn't track the method set_source_stream() itself (it could show a decrease of runtime after the first call).
Here comes a little self-contained ABAP program to test the functionality. It works well on our system with SAPKB70012.
Thanks and regards,
Rüdiger
* --- Test usage of a dynamically given non-workbench XSLT program
report zz_test_cl_xslt_processor.
data:
* iXML master
go_xml type ref to if_ixml,
* iXML stream factory
go_sf type ref to if_ixml_stream_factory.
load-of-program.
go_xml = cl_ixml=>create( ).
go_sf = go_xml->create_stream_factory( ).
start-of-selection.
perform start.
* --- Start
form start.
data: lo_source type ref to if_ixml_document,
 lo_result type ref to if_ixml_document,
 lo_processor type ref to cl_xslt_processor,
 lv_p type progname,
 lo_ex type ref to cx_xslt_exception.
perform get_source changing lo_source.
create object lo_processor.
try.
* Set source
 lo_processor->set_source_node( lo_source ).
* Set result
 lo_result = go_xml->create_document( ).
 lo_processor->set_result_document( lo_result ).
* This could be time-critical, the creation of a dynamical XSLT prog?
 perform set_transformation using lo_processor
 changing lv_p.
* call xslt-proc
 lo_processor->run( lv_p ).
* Display result
 call function 'SDIXML_DOM_TO_SCREEN'
 exporting
 document = lo_result
 title = 'Result of Transformation'
 exceptions
 no_document = 1
 others = 2.
 catch cx_xslt_exception into lo_ex.
 sy-msgli = lo_ex->get_text( ).
 message sy-msgli type 'I'.
endtry.
endform. "start
* --- Set XSLT transformation from stream
form set_transformation using io_processor type ref to cl_xslt_processor
 changing cv_p type progname.
data: lo_trans type ref to if_ixml_istream.
* sv_p contains temp. name of XSLT program after first call
statics: sv_p type string.
if sv_p is initial.
* It seems that the name can be buffered on appserver level?
 import progname to sv_p
 from shared buffer indx(zx) id 'ZZ_TEST_XSLT_PROC'.
 if sv_p is initial.
 sv_p = 'X'.
 endif.
endif.
* Provide the stream containing the XSLT document (as a stream)
perform get_transformation changing lo_trans.
* Set transformation
io_processor->set_source_stream( exporting stream = lo_trans
 changing p = sv_p ).
* Buffer progname on server - seems to work
export progname from sv_p
 to shared buffer indx(zx) id 'ZZ_TEST_XSLT_PROC'.
* string -> c move necessary, since xslt-proc-interface doesn't use
* the generic type csequence for program name
cv_p = sv_p.
endform. "set_transformation
* --- Parse a source given as string into an if_ixml_document
form get_source changing co_src type ref to if_ixml_document.
data: lv_s type string,
 lo_stream type ref to if_ixml_istream,
 lo_parser type ref to if_ixml_parser.
concatenate
`<?xml version="1.0" encoding="iso-8859-1"?>`
`<countings filiale="2412" invnu="TIEFKUEHL SEPT.07">`
`<count recNum="1" gid="1" ean="59111828843" menge="1"`
`preis="0" recNumFrom="1"></count>`
`</countings>`
into lv_s.
* Eingabestream erzeugen und in if_ixml_document abbilden
lo_stream = go_sf->create_istream_string( lv_s ).
co_src = go_xml->create_document( ).
lo_parser = go_xml->create_parser( document = co_src
 istream = lo_stream
 stream_factory = go_sf ).
lo_parser->parse( ).
endform. "get_source
* --- Put the transformation given as string into an if_ixml_istrean
form get_transformation changing co_trans type ref to if_ixml_istream.
data: lv_s type string.
concatenate
`<?xml version="1.0" encoding="iso-8859-1"?>`
`<xsl:transform version="1.0"`
` xmlns:xsl="http://www.w3.org/1999/XSL/Transform"`
` xmlns:asx="http://www.sap.com/abapxml">`
`<xsl:strip-space elements="*"></xsl:strip-space>`
`<xsl:template match="countings">`
` <asx:abap>`
` <asx:values>`
` <SELOPT>`
` <WERKS><xsl:value-of select="@filiale"></xsl:value-of></WERKS>`
` <INVNU><xsl:value-of select="@invnu"></xsl:value-of></INVNU>`
` </SELOPT>`
` <COUNTINGS>`
` <xsl:for-each select="count">`
` <ZSRS_ZWSTI_LINE>`
` <MATNR></MATNR>`
` <EAN11><xsl:value-of select="@ean"></xsl:value-of></EAN11>`
` <MAKTX></MAKTX>`
` <MENGE><xsl:value-of select="@menge"></xsl:value-of></MENGE>`
` <MEINH></MEINH>`
` <UNAME></UNAME>`
` <EXVKW></EXVKW>`
` <WAERS></WAERS>`
` <FF></FF>`
` <GID><xsl:value-of select="@gid"></xsl:value-of></GID>`
` <RECNUM><xsl:value-of select="@recNum"></xsl:value-of></RECNUM>`
` <RECNUM_FROM><xsl:value-of select="@recNumFrom"></xsl:value-of></RECNUM_FROM>`
` <REF_RECNUM><xsl:value-of select="@refRecNum"></xsl:value-of></REF_RECNUM>`
` </ZSRS_ZWSTI_LINE>`
` </xsl:for-each>`
` </COUNTINGS>`
` </asx:values>`
` </asx:abap>`
`</xsl:template>`
`</xsl:transform>`
into lv_s.
co_trans = go_sf->create_istream_string( lv_s ).
endform. "get_transformation
Edited by: Rüdiger Plantiko on Jul 4, 2008 10:25 AM

Problem with Enable scalable feature of XSLT processor

Hi Gurus,
I'm using BI Publisher 10.1.3.4.1. I've having a report, when running in a specific sequence (i.e. after running with XML dataset 1 then dataset 2), will yield an error. Here is the log I got in the xdo.log.
[061411_110902953][][EXCEPTION] java.lang.reflect.InvocationTargetException
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at oracle.apps.xdo.common.xml.XSLT10gR1.invokeProcessXSL(Unknown Source)
     at oracle.apps.xdo.common.xml.XSLT10gR1.transform(Unknown Source)
     at oracle.apps.xdo.common.xml.XSLT10gR1.transform(Unknown Source)
     at oracle.apps.xdo.common.xml.XSLTWrapper.transform(Unknown Source)
     at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(Unknown Source)
     at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(Unknown Source)
     at oracle.apps.xdo.template.FOProcessor.createFO(Unknown Source)
     at oracle.apps.xdo.template.FOProcessor.generate(Unknown Source)
     at oracle.apps.xdo.servlet.RTFCoreProcessor.transform(RTFCoreProcessor.java:91)
     at oracle.apps.xdo.servlet.CoreProcessor.process(CoreProcessor.java:256)
     at oracle.apps.xdo.servlet.CoreProcessor.generateDocument(CoreProcessor.java:81)
     at oracle.apps.xdo.servlet.ReportImpl.renderBodyHTTP(ReportImpl.java:678)
     at oracle.apps.xdo.servlet.ReportImpl.renderReportBodyHTTP(ReportImpl.java:255)
     at oracle.apps.xdo.servlet.XDOServlet.writeReport(XDOServlet.java:270)
     at oracle.apps.xdo.servlet.XDOServlet.writeReport(XDOServlet.java:250)
     at oracle.apps.xdo.servlet.XDOServlet.doGet(XDOServlet.java:178)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
     at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
     at oracle.apps.xdo.servlet.security.SecurityFilter.doFilter(SecurityFilter.java:86)
     at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)
     at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
     at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
     at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
     at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
     at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
     at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
     at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
     at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.NullPointerException
     at oracle.xdo.parser.v2.FilePageManager.pageLength(FilePageManager.java:242)
     at oracle.xdo.comp.CXMLStream.ensureReadCapacity(CXMLStream.java:1543)
Then I tried turning off "Enable scalable feature of XSLT processor" (under the FO Processing, default is ON) This error cannot be reproduced again (i.e. my report can run in whatever sequence without an error).
Would anyone explain to me what actually is the difference between setting the "Enable scalable feature of XSLT processor" to true and false. I'll be running the same report template with thousands of pages in some cases and I'm anxious whether turning OFF the "scalable feature" will make the performance suffer.
Thanks in advance,
Jonathan

Are you running Enterprise Edition? I believe flashback database is only available with Enterprise.

XSLT processor

which XSLT processor do you use ? Xalan , cocoon ?
please suggest a good XSLT processor

BTW, i have not seen you in the forum for the past
3-4 days....
http://forum.java.sun.com/thread.jspa?threadID=628173

Running NetWeaver's XSLT processor from Oxygen

Hello
I am using Oxgen XML Editor (version 12.1, build 2011012011) to create my XSLT mappings. Having tested these mappings successfully offline they are imported onto our SAP-PI ( SAP NetWeaver 7.01 ). However, sometimes mappings that work in Oxygen fail on SAP-PI. Therefore, I would like to use NetWeaver's XSLT processor as Custom Engine within Oxgen.
Triggered by the blog of Thorsten Nordholm Søbirk
Running NetWeaver's XSLT processor from XMLSpy
I copied the archive sapxmltoolkit.jar into the lib directory of the Oxygen installation path. Next I went to menu Options -> Preferences -> XML -> XSLT/FO/XQuery -> Custom Engines and defined the following settings:
Working Directory = .
Command Line = C:Program FilesJavajdk1.6.0_07 injava -cp
"C:Program FilesOxygen XML Editor 12libsapxmltoolkit.jar";
com.sap.engine.lib.xsl.Process
-xml="C:     empz_tempinput.xml"
-xsl="C:     empz_tempstylesheet.xsl"
-out="C:     empz_tempoutput.xml"
In addition, within the Transformation Options I set:
javax.xml.transform.TransformerFactory=com.sap.engine.lib.jaxp.TransformerFactoryImpl
For the sake of simplicity I used a plain stylesheet without any Java extensions. When I delete file "output.xml" in "C:     empz_temp" and execute the transformation the file is recreated. Thus, I am sure that the NetWeaver XSLT processor has been used.
However, instead of hard-coding filenames and pathes I would like to use the built-in variables of Oxygen like "$" etc. Most of the XSLT mappings use a Java extension which is located in the same directory as sapxmltoolkit.jar (C:Program FilesOxygen XML Editor 12lib).
There are 2 major problems that I am facing now:
(1) How must the Command Line look like so that I can use Oxygen's built-in variables as input for -xml, -xsl and -out?
(2) How must the Command Line look like so that the Java extension archive is recognized?
Your help and valuable input is very much appreciated.
Regards
Uwe

hi,
this is how we use it with Stylus Studio, also with external libraries
c:\program files\java\jre1.5.0_22\bin\java.exe -cp "Y:\xivaluemappingproxy_stylusstudio.jar";"c:\sapxmltoolkit.jar";"Y:\XIFramework.jar";"Y:\jms.jar";"Y:\sapjco.jar";"c:\ExtendedValueChange.jar" com.sap.engine.lib.xsl.Process -xsl=%2 -xml=%1 -out=%3

IDoc to cXML using built-in SAP XSLT Processor

Hi ABAP experts,
i have a requirement to send an IDoc to an external system, the external system expecting it to be in cXML standard - without using XI/PI
has someone of you done this before?
I was looking at the option to utilize the built-in SAP XSLT processor (CALL TRANSFORMATION) since it supports XML to XML and ABAP to XML transformations
so the flow would either be
IDoc --> XSLT --> cXML (preferred)
IDoc --> XML (using XML port) --> XSLT --> cXML
is this possible?
Also, can the cXML be sent using the XML HTTP port in we21?
Your tips suggestions would be highly appreciated

Hello
Have you had a look at class CL_IDOC_XML1? This class does the transformation IDoc -> XML for you.
The next step would be to create the required XSLT transformation for the mapping IDoc-XML -> cXML.
Regards
Uwe

XSLT Processor Bug? format-number() on large numbers

For numbers 100,000,000.00 and higher, I'm getting extra digits and rounding errors.
How can I use some custom Java code in the XSL stylesheet so the correct value is displayed (i.e. w/o rounding)? I'm getting a value of 100000000.00 and I need to insert the commas. Sometimes the correct value is displayed, other times, additional numbers are appended and the amount is rounded.

The XSLT processor uses java.text.DecimalFormat under the covers as the XSLT 1.0 specification suggests. I would imagine any problems with format-number() actually boil down to problems with java.text.DecimalFormat.
You can use Java Extension functions to perform custom Java in your stylesheet.
See the file .\extfunc.html in the root directory of the XML Parser for Java V2
distribution.

XSLT 2.0 processor

Similar Messages

Maybe you are looking for