Problem facing in XSL transformation

Hi,
I have deployed my j2ee application on SAP, i'm using xalan transformer that SAP does not support. I used com.sap.engine.lib.jaxp.TransformerFactoryImpl file in place of xalan, but still it gives me following error:
javax.xml.transform.TransformerConfigurationException: javax.xml.transform.TransformerException: javax.xml.transform.TransformerException: xsl:param is not allowed in this position in the stylesheet! at org.apache.xalan.processor.TransformerFactoryImpl.newTemplates(TransformerFactoryImpl.java:984)
I'm not attaching all details of exception here, can anybody help me in what should I use in place of <xsl:param> to avoid this error.
looking forward for the replies....
thanks in advance
--saplearner

check SAP Note 894884.
Hot deployment is not supported for KM development.
You better develop on another development portal where restarts do not affect the end users.
check these threads http://forums.sdn.sap.com/message.jspa?messageID=8283651
http://forums.sdn.sap.com/message.jspa?messageID=3548968
Regards
Mahesh

Similar Messages

XSL transform sort problem in 1.5

I am having problems applying an XSL transform to some XML data I have under the 1.5 JRE.
Under 1.4.2 (and in several tools and browsers), the transform works correctly. In 1.5,
<xsl:sort...> directives don't seem work correctly. Here's a simplified version of my
code. Assume that the generateXMLReport outputs an XML document to a stream.
public void generateHTMLReport( OutputStream out, String strXslSheet ){
     File f = new File( strXslSheet );
     if( f.exists() ){
          ByteArrayOutputStream bos = new ByteArrayOutputStream();
          // Generate the XML data we will work from
          generateXMLReport( bos );
          bos.flush();
          // Convert the XML to HTML by applying an XSL transform
          ByteArrayInputStream bis = new ByteArrayInputStream( bos.toByteArray() );
          TransformerFactory tFactory = TransformerFactory.newInstance();
          Transformer transformer = tFactory.newTransformer( new StreamSource( strXslSheet ) );
          transformer.transform( new StreamSource( bis), new StreamResult( out ) );
}Here's an XSL template:
<xsl:template name="totalTable">
     <xsl:param name="matchSet"/>
     <xsl:variable name="maxValue">
     <xsl:for-each select="$matchSet">
     <xsl:sort select="total" data-type="number" order="descending"/>
     <xsl:if test="position() = 1">
          <xsl:value-of select="number( total )" />
         </xsl:if>
         </xsl:for-each>
         </xsl:variable>
</xsl:template>If I remove the sort directive, I get the first value in the list, as I would expect.
Other 'for-each' loops behave similarly. The problem in 1.5. When I run against 1.4.2,
the transformation works fine.

Show us the code please. Not the WHOLE code, just an example that demonstrates what you're seeing. I've never seen the problem you're encountering, but I rather doubt that it's a failing in the api. More than likely it's a semantic of how you're doing the listener but that's a guess on my part. Let's see what you have and go from there.
PS.

XSL Transformation crashes DW CS3

Whenever I select XSL Transformation from any of the menus,
it crashes DW CS3 asking the typical, "do you want to tell
microsoft about this error."
Anyone have this problem with using XSL Transformations? I'm
thinking about reinstalling DW to see if it fixes the problem.
Thanks

Forgot to mention that this is a Windows XP SP2 machine.

XSL transformation related point

Hi All,
Morning, need some assistance with this issue we are facing during XSL transformation,
During the XSL transformation we need to access mapping file lets say country-code.txt which has the details as mentioned below:
US=USA
UK=Great Britain
Now when the input data value comes as US we need to map the output tag in the xsl with the value USA at run time & if input is Uk then output tag value should be Great Britain
2.Also in another file say login-details.txt we have maintained the user-name & password like below:
user-name='Test'
password='welcome'
This also we need to get the values in the xsl transformation file within the BPEL process so that at Run Time these could be got from the file ( since if we hard code in the xsl file within the BPEL process whenever the instance login details changes everytime we would have to change in the process and re deploy again)
1.Now in Soa Suite 10g is there a way or method/steps wherein from the xslt mapping file within the BPEL process we could make a call or access these files. Also on the application server/unix directory where do we need to physically put these files at which directory location ..if this is possible.
2.Also could a similar scenario be achieved in SOA Suite 11g
Could someone please help us with this as we are currently stuck with this situation..
with regards as always..

Hi ,
Thanks for your response first...have mentioned the details below
***xsl mapping ****
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:get="http://www.oracle.com/XSL/Transform/java/customclass" version="1.0">
<FinalCountryCode>
<xsl:variable name="countryCode" select="INPUT_COUNTRY_CODE"/>
<xsl:value-of select="get:getCode($countryCode)"/>
</FinalCountryCode>
****class defintion mentioned below****
(this is a custom java class created where we could try accessing the file named country_code.txt and we would try calling the getCode function of this java class from the xsl mapping as above.)
import java.io.FileInputStream;
import java.util.*;
public class customclass
     public static String getCode(String p_str_CountryCode)
          Properties o_countryCode = new Properties();
          String v_countryCode = null;
          FileInputStream o_Code = new FileInputStream("country_code.txt");
          o_countryCode.load(o_Code);
          v_countryCode = o_countryCode.getProperty(p_str_CountryCode);
          return v_countryCode;
country_code.txt file would have details like this:
US=USA
UK=Great Britain
So during the SOA Run time if the value for INPUT_COUNTRY_CODE comes as US the final tag CountryCode3Gid should have the value as USA
1.Now where do we need to physically put the file name country_code.txt (having the country code mappings) on the application server in Soa 11g, so that it could be accessed during Run Time.
2.Also where do we put customclass so that it could be accessed during SOA Run Time
3.Also in Soa 10g & Soa 11g is there a better method or any other way/steps within Jdev and also during SOA run time that this functionality could be achieved (means call an external file which stores the mapping values which need to be referred during xsl mapping within BPEL process)
4.We are not sure whether this would be feasible method and how to make this work in 10g as well as 11g
thanks

Problems faced when using xsl:include and extension functions

I am Working in XML and XSLT using Oracle's XML Parser V2.
Previously i had worked in Microsoft technology using MSXMLParser.
I am facing some problems in XSLT. They are as below...
1. Using <xsl-include href="Somexsl.xsl">
the oraclexmlparser processor is giving the error : XSL-1002: Error while processing include XSL file (no protocol: Submenu.xsl).
* Can u tell me why i am getting this error, and what is the fix for this.
The same case with <xsl:import> too.
2. In case i have to write some functions in the previous WD of xsl i used these statements
<?xml version='1.0'?>
<!DOCTYPE PageRoot SYSTEM "../../Common/dtd/PageNavBar.dtd">
<xsl:stylesheet
xmlns:xsl="http://www.w3.org/TR/WD-xsl"
xmlns:html="http://www.w3.org/TR/REC-html40"
result-ns="">
<xsl:script xmlns:xsl="uri:xsl"><![CDATA[
var strWebContentPath = "/SurSITE/Content/";
var strWebImagePath = "/SurSITE/sursitegraphics/";
function IncScript()
return "<script language='javascript' src='/SurSITE/Includes/avalidations.js'></script>";
]]>
</xsl:script>
To call the function i used this
<xsl:eval no-entities='true'> IncScript();</xsl:eval>
* Can u tell me how do i do this now, i tried with the code above using the current name space (<xsl:stylesheet version="1.1"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform" />)
Please use the example given above.
I will be very greatfull to u if u can give me some suggestion or help for the above said problems.
Thanking you and eagerly waiting for your reply(s).
null

The current version is "1.0" not "1.1"
You haven't included the code for what your <xsl:include>
statement looks like, which seems to be what it's complaining
about...
XSLT 1.0 has no <xsl:eval>, this is a microsoft specific tag
from a pre-XSLT-1.0 version.
XSLT 1.0 has no <xsl:script> element either.

Error: "... is not a table ..." XML not correctly interpreted after XSL-transformation. Table row quantity problem.

Hey guys, this is one of my xml-elements:
Jaspreet Sohi 12 18 Juliane Lenz 11 17 Sophie Charlotte Stender 10 15 Rosbeh Hamidzadeh Khayyat 12 17 Lion Stoldt 12 17 Mats Lucas Meincke 6 8 Bero Luke Vincent Ernst 6 8 Cedric Roth 6 8 Soner Cantay 6 8 The following XSL Transformation I use once for transforming all "m" tags and once in order to transform all "j" tags. Please imagine the CSL-code below to be duplicated exactly. Only the "jungs"-table-Tag is replaced by "mädchen" and all underscores _j are replace by _m. As well all "select="j[@..." parts are replaced by "select="m[@...". 1 2 3 The code is very easygoing I think and not difficult to understand. As I said, I use it twice - for both transformations. The very, extremely weird thing, my problem, is that one transformation works perfectly in InDesign and a table is created for all "kategorie"-tags (all is set within a for-each loop). But the second script does not work! I simply do not get this I can't understand it. I've tried more than anything. InDesign sais (in German, so translated based on assumption) "jungs is an invalid table element or is displayed in wrong order". The second strange thing is that I can replace my "aid:trows" attribute by any number, e.g. "10" and immediately the script works fine (as there are never more than 6 "j" tags in my XML so that never the table has more than 6 rows"). But it does not want to work correctly with the actual number, my variable "rows_j". These are my variables: They are all defined before the tables for m and j are created. So finally, why (the heck) is one table created and interpreted perfectly whereas the second - immediately following the first in the XSL.script as an EXACT copy of the first - results in an error? As i've already said, I've tried really everything. For example the script works also when one of the parts "" is randomly deleted from the script. Removing one of these parts directly makes the script working. Just one of my attempts to understand the thing but this has only shown that none of these parts "cell to end-for-each" includes an error. I'm really desperate and looking forward to being rescued by one of you geniuses :)

Hah, No worries. The forum software is, well, different.
What would be better, though, would be a sample ID file, any XSLT/XLT files you use, and a bit of data exactly as you have it (pre-transform state). ZIP it up, upload to say dropbox.com and feel free to send me a private message for the download link.
Too many times there is something different between samples pasted into a post and the real thing that it is sometimes less useful time-wise. I'll keep it private, of course. Then we can communicate via PMs or email until we can (hopefully) arrive together at a solution, then post what that solution is in the forum to benefit others.
Thank you, Mike

Xsl transformation from version1 to version2, problem with namespaces

Guys!
In my current project we need to have an interface in Oracle ESB which is build on lets say a wsdl version1 and an interface build on wsdl version2.
In esb i need to define a transformation which will transform the request on version1 to version2. Because the xsd for the operation is really huge (+1000 items) i made some templates in xsl to do most of the work, works great..only i'm having a few issues now.
To re-order items from source to target i do the next in a template
<nameGroep>
<xsl:copy-of select="andhere the xpath from source"/>
<xsl:copy-of select="andhere the xpath from source"/>
<xsl:copy-of select="andhere the xpath from source"/>
</nameGroep>The only problem from the xsl:copy-of is, it also copies the namespace along. So if my target document uses an other namespace, it fails.
To correct this i hoped i could make use of <xsl:namespace-alias> but this doesn't work on a literal/text tag (hope i explain this correct).
Other option is, for every element do something like
[code[
<elementname>
<xsl:value-of select=""/>
</elementname>
but this will create the <elementname> always in the target whether or not it's in the source. You could do a check to see if it's in the source, but this isn't a solution because then i need to check for every 1000+ item in the source document, so..we skip this idea.
So i reach a point where im still searching for a good solution and hoped you guys could help me a bit with it.
If the problem isn't explain well please say so, and i will add extra info.

Guys!
In my current project we need to have an interface in Oracle ESB which is build on lets say a wsdl version1 and an interface build on wsdl version2.
In esb i need to define a transformation which will transform the request on version1 to version2. Because the xsd for the operation is really huge (+1000 items) i made some templates in xsl to do most of the work, works great..only i'm having a few issues now.
To re-order items from source to target i do the next in a template
<nameGroep>
<xsl:copy-of select="andhere the xpath from source"/>
<xsl:copy-of select="andhere the xpath from source"/>
<xsl:copy-of select="andhere the xpath from source"/>
</nameGroep>The only problem from the xsl:copy-of is, it also copies the namespace along. So if my target document uses an other namespace, it fails.
To correct this i hoped i could make use of <xsl:namespace-alias> but this doesn't work on a literal/text tag (hope i explain this correct).
Other option is, for every element do something like
[code[
<elementname>
<xsl:value-of select=""/>
</elementname>
but this will create the <elementname> always in the target whether or not it's in the source. You could do a check to see if it's in the source, but this isn't a solution because then i need to check for every 1000+ item in the source document, so..we skip this idea.
So i reach a point where im still searching for a good solution and hoped you guys could help me a bit with it.
If the problem isn't explain well please say so, and i will add extra info.

XSL Transformation enconding problem?

Hi everybody.
I have a strange problem with JDev 9.0.2.829 concerning XSL Transformation:
I just tried to make the step from JDev 3.2.3 to 9i, imported my existing project and set up JDev 9 for use with XalanJ2 and Xerces2. Everything works fine except:
If I transform XML data to HTML that contains characters with an ASCII code >127 the whole string appears multiple times (2x or 3x) in the generated HTML.
The data is read from an Oracle DB with UTF8 encoding, all my stylesheets and JSPs are UTF-8 encoded. JDev9 is set to use UTF-8 encoding.
No compilation errors, no warnings.
The same code and stylesheets work perfectly in JDev 3.2.3, deployed into Topmcat 4.0.4 and IBM WebSphere 3.5.4.
What am I missing?
Thanks in advance!
Ralf Steppacher

OK, I found the culprit.
The JSPWriter is broken and produces the faulty output when fed with UTF-8 encoded character data. The problem disappears when all character data is buffered in a ByteArrayOutputStream first (without a special encodung schema given) and then written as a string through the JSPWriter.
Ralf

Weblogic 6.0 XSL Transformation whitespace Problem

I am having a problem with the HTML that is coming out of my XSL
transformation in Weblogic 6.0, service pack 2.
The problem occurs in a place where the </TD> tag is preceded by a
carriage return in the HTML code that is generated. This causes an
extra blank line in the browser (the famous "whitespace bug" in the
browsers).
I was able to control this when I created my own HTML by moving the
</TD> tag up to the previous line. I no longer have this control
since I am using XML and XSL - Weblogic is doing the transformation to
HTML for me. Even if I move the </TD> tag in the XSL, the HTML that
is outputted reformats it and puts the </TD> tag on the next line.
Has anyone else seen this problem? I'm wondering if there is some way
that you can tell the transformer to concatenate the HTML?
Any info would be appreciated.
Thanks,
Larry

[att1.html]

Problems with xsl transformation

Hi,
I have an XSL to transform an XML to HTML code.
I want my HTML to be ACCESSIBLE.
All is working ok, but the <html> tag have two or three attributtes that make de code no ACCESSIBLE.
This is a part of the XSL code:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:fn="http://www.w3.org/2005/xpath-functions" xmlns:xdt="http://www.w3.org/2005/xpath-datatypes">
     <xsl:output method="xhtml" version="1.0" encoding="UTF-8" indent="yes" standalone="no"/>
<xsl:include href="barraSuperior.xsl"/>
     <xsl:include href="cabecera.xsl"/>
     <xsl:include href="menu.xsl"/>
     <xsl:include href="enllacosDestacats.xsl"/>
     <xsl:include href="contenido.xsl"/>
     <xsl:include href="barraBanners.xsl"/>
     <xsl:include href="pie.xsl"/>
     <xsl:variable name="homeWeb">http://172.16.67.119:8080/Biblioteques/xslt/V53CapSetmana</xsl:variable>
     <xsl:variable name="idioma"><xsl:value-of select="xmlData/config/idioma"/></xsl:variable>
     <xsl:variable name="literals" select="document(concat($homeWeb,'/traduccions/',$idioma,'.xml'))"/>
     <xsl:template match="/">
          <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="{$idioma}" lang="{$idioma}">
               <head>
                    <title>
<body>
                    <xsl:call-template name="barraSuperior"/>
                    <xsl:call-template name="cabecera"/>
                    <div id="wrapper">
                         <div id="columna0">
                              <xsl:apply-templates select="xmlData/menuLateral/contingutVignette/contingut/llista"/>
                         </div>
                         <xsl:call-template name="contenido"/>
                    </div>
                    <xsl:call-template name="pie"/>
               </body>
          </html>
     </xsl:template>
</xsl:stylesheet>
This is a part of the HTML result:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<html xmlns="http://www.w3.org/1999/xhtml" xmlns:fn="http://www.w3.org/2005/xpath-functions" xmlns:xdt="http://www.w3.org/2005/xpath-datatypes" xmlns:xs="http://www.w3.org/2001/XMLSchema" xml:lang="ca" lang="ca">
     <head>
          <title>B cap de setmana</title>
</head>
<body>
</body>
I want the <html> to be like this:
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="ca" lang="ca">

Use the exclude-result-prefixes attribute in your xsl:stylesheet element.

XSL transformation with xsl:import generates exceptions

I am using the Schematron's basic XSL file basic-schematron.xsl to validate the XML format of one of our data files. The XSL file looks something like this
================
<xsl:stylesheet
version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:axsl="http://www.w3.org/1999/XSL/TransformAlias">
<xsl:import href="skeleton1-5.xsl"/>
<xsl:template name="process-prolog">
<axsl:output method="text" />
</xsl:template>
==================
But, the validation fails while trying to run the transformation on my Schematron input file using this basic-schematron.xsl with java.lang.NoSuchMethodError:
======= OUTPUT ============
Markup Error: no match attribute on <key> outside <rule>
Exception in thread "AWT-EventQueue-0" java.lang.NoSuchMethodError: GregorSamsa.process$dash$root(Lcom/sun/org/apache/xalan/internal/xsltc/DOM;Lcom/sun/org/apache/xml/internal/dtm/DTMAxisIterator;Lcom/sun/org/apache/xml/internal/serializer/SerializationHandler;ILjava/lang/Object;)V
     at GregorSamsa.applyTemplates()
     at GregorSamsa.applyTemplates()
     at GregorSamsa.transform()
     at com.sun.org.apache.xalan.internal.xsltc.runtime.AbstractTranslet.transform(AbstractTranslet.java:594)
     at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:640)
     at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:279)
     at com.solipsa.xsdvalidator.XSDValidator.validateSchematron(XSDValidator.java:137)
     at com.solipsa.xsdvalidator.XSDValidator.validate(XSDValidator.java:181)
     at com.solipsa.xsdvalidator.XSDValidatorUI.jButton1ActionPerformed(XSDValidatorUI.java:244)
     at com.solipsa.xsdvalidator.XSDValidatorUI.access$300(XSDValidatorUI.java:21)
     at com.solipsa.xsdvalidator.XSDValidatorUI$4.actionPerformed(XSDValidatorUI.java:140)
     at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1849)
     at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2169)
     at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
     at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
     at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:234)
     at java.awt.Component.processMouseEvent(Component.java:5488)
     at javax.swing.JComponent.processMouseEvent(JComponent.java:3093)
     at java.awt.Component.processEvent(Component.java:5253)
     at java.awt.Container.processEvent(Container.java:1966)
     at java.awt.Component.dispatchEventImpl(Component.java:3955)
     at java.awt.Container.dispatchEventImpl(Container.java:2024)
     at java.awt.Component.dispatchEvent(Component.java:3803)
     at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4212)
     at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3892)
     at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3822)
     at java.awt.Container.dispatchEventImpl(Container.java:2010)
     at java.awt.Window.dispatchEventImpl(Window.java:1766)
     at java.awt.Component.dispatchEvent(Component.java:3803)
     at java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
     at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:234)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
     at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
============= OUTPUT ==============
I tried the individual JAXP 1.3 for J2SDK 1.4.2 (Using the -Djava.endorsed.dirs JVM param) and tried the JDK 1.5.0_02 which has JAXP 1.3 inbuilt and they all fail.
I tried the above with separate Xalan/Xerces jar files, and then it works fine.
The problem seems to be somthing specific to the JAXP 1.3 environment. I can provide more details, if required. Any help is highly appreciated.

One morning your code woke up and found it had been transformed into a giant insect.
But seriously, here's the name of the method that doesn't exist:GregorSamsa.process$dash$rootIs GregorSamsa your class? Maybe your server has an old version of it which is missing that method? (Or: those $ signs look strange to me, maybe they are a mistranslation of some other character?)

XSL Transformation between arrays

Dear all
I create to XSD for my variables:
<?xml version="1.0" encoding="UTF-8" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:ns="http://www.asre-andishe.com/Inspec/General"
targetNamespace="http://www.asre-andishe.com/Inspec/General"
elementFormDefault="qualified">
<xsd:complexType name="AgentArrayType">
<xsd:sequence>
<xsd:element name="Agent" type="ns:AgentType" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="AgentType">
<xsd:sequence>
<xsd:element name="user" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="Agent" type="ns:AgentType"></xsd:element>
<xsd:element name="AgentsArray" type="ns:AgentArrayType"></xsd:element>
</xsd:schema>
and the other one:
<?xml version="1.0" encoding="UTF-8" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:ns="http://www.asre-andishe.com/Inspec/DetermineInspec/retrive/relam"
targetNamespace="http://www.asre-andishe.com/Inspec/DetermineInspec/retrive/relam"
elementFormDefault="qualified">
<xsd:complexType name="RelamAgentType">
<xsd:sequence>
<xsd:element name="user" type="xsd:string" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
<xsd:element name="RelamAgents" type="ns:RelamAgentType"></xsd:element>
</xsd:schema>
I create two empty variable and then initialized the second variable
<RelamAgents>
<user>john</user>
<user>david</user>
<user>jack</user>
</RelamAgents>
after that i use a transformation XSL and the second variable has been filled without no problem.
<AgentsArray>
<ns0:Agent>
<ns0:user>john</ns0:user>
</ns0:Agent>
<ns0:Agent>
<ns0:user>david</ns0:user>
</ns0:Agent>
<ns0:Agent>
<ns0:user>jack</ns0:user>
</ns0:Agent>
</AgentsArray>
but when i fill the first variable by receiving the output parameter from a service call, the XSL transformation did not work at all and the second variable remains empty.
I have checked the first variable and i am sure that it is not null and it has the same vale:
<RelamAgents>
<user>john</user>
<user>david</user>
<user>jack</user>
</RelamAgents>
Would anybody please help me with this problem?
Thank you very much

Hi,
receiving the output parameter from a service call, the XSL transformation did not workNamespaces... Check the namespaces the service call is using and see if they match with the XSL is expecting...
Cheers,
Vlad

XSL Transformation error source

I am using MII 12.0 and I am getting the following error in the log file:
javax.xml.transform.TransformerException: javax.xml.transform.TransformerException: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: An attempt to write after the stream had been closed.
The problem is that I am not using and XSL transforms that I know of. What BLS action might generate this error other than the obvious XSL Transformation Action?
Thanks.
...Sparks

I found this thread:
[Re: IDOC error|Re: IDOC error]
Is your system set up to receive any idocs?
Edited by: Christian Libich on Feb 8, 2010 10:00 PM

XSL Transformation Design View

Hello together,
we find an issue with design view of xsl transformation. When we use the design view serveral configurations and mappings where edited and deleted. For example <xsl:stylesheet version="2.0" change to version="1.0" and the call of EBMHeader-Template was deleted.
Has anybody the same problem? Our are everybody a "h a r d c o r e" coder and use the source view ;-)
Greetings from Karlsruhe
Marcel
PS: It's a little bit tricky to show the design view. We must switch between diffent xslt to see the design.

when you open the imported xsd in the browser, you do get a xsd shown up ?
and when you download the xsd locally and validate it, it is valid?

XSL Transformation - cut asx:abap and asx:values

Hey all,
I'm using a XSL Transformation to create a XML-File from an internal table.
My problem is, that the transformation automatically puts the two tags "<asx:abap xmlns:asx="http://www.sap.com/abapxml">" and "<asx:values>" at the beginning of my file (or string):
<?xml version="1.0" encoding="iso-8859-1" ?>
<asx:abap xmlns:asx="http://www.sap.com/abapxml">
<asx:values>
<ROOT>
</ROOT>
</asx:values>
</asx:abap>
Does anyone have any idea how I can easily suppress these lines?
The best course would be of course an XSL statement.
Thanks and regards,
Martin.

Will using a Simple Transformation help your case ?

Problem facing in XSL transformation

Similar Messages

Maybe you are looking for