Detroubulator: RESOURCE_NOT_FOUND when testing XSLT mapping

Hello Everybody
I have tried to test a XSLT mapping on SAP-XI (7.0, service pack 14) using Detroubulator (1.1.0):
- JRE = jre1.6.0_03
- JCo = 2.1.8
- JUnit = junit-4.4.jar
- aii_map_api.jar was copied from XI server to /detroubulator/lib
However, running my test file I receive the following error:
Detroubulator version 1.1.0, copyright 2006, 2007 AppliCon A/S
Test file: test_xslt.xml
04.02.2008 07:36:08 org.detroubulator.server.XIServerRFCImpl configure
INFO: JCo version: 2.1.8 (2006-12-11)
04.02.2008 07:36:09 org.detroubulator.core.Launcher terminate
SCHWERWIEGEND: Termination requested with message: Server error: RESOURCE_NOT_FOUND,E,205,0,sap.invoic02.tradacom.1993.invoic.xsl,http://lindt.com/customer/defaults,829eeb5c-6af6-3be5-838d-0a40ea0fdfcb,-1
04.02.2008 07:36:09 org.detroubulator.core.Launcher terminate
SCHWERWIEGEND: org.detroubulator.server.ServerException: RESOURCE_NOT_FOUND,E,205,0,sap.invoic02.tradacom.1993.invoic.xsl,http://lindt.com/customer/defaults,829eeb5c-6af6-3be5-838d-0a40ea0fdfcb,-1
 at org.detroubulator.server.XIServerRFCImpl.executeMapping(Unknown Source)
 at org.detroubulator.server.XIServerRFCImpl.executeXSLTMapping(Unknown Source)
 at org.detroubulator.mappingprograms.XSLTMapping.execute(Unknown Source)
 at org.detroubulator.core.TestSuite.execute(Unknown Source)
 at org.detroubulator.core.Launcher.start(Unknown Source)
 at org.detroubulator.core.Launcher.main(Unknown Source)
Server error: RESOURCE_NOT_FOUND,E,205,0,sap.invoic02.tradacom.1993.invoic.xsl,http://lindt.com/customer/defaults,829eeb5c-6af6-3be5-838d-0a40ea0fdfcb,-1
The crucial parts of the test file are shown below:
<?xml version="1.0" encoding="UTF-8"?>
<testsuite>
 <server>
 <configuration>
 </configuration>
 </server>
 <program type="xslt">
 <configuration>
 <parameter name="name">sap.invoic02.tradacom.1993.invoic.xsl</parameter>
 <parameter name="ns">http://lindt.com/customer/defaults</parameter>
 <parameter name="swcv.id">829eeb5c6af63be5838d0a40ea0fdfcb</parameter>
 </configuration>
 </program>
 
 <reporting>
 <testreport type="console">
 <configuration>
 <parameter name="dumpdir">dumped_output</parameter>
 </configuration>
 </testreport>
 <testreport type="xml">
 <configuration>
 <parameter name="file">sample_report_xslt.xml</parameter>
 <parameter name="dumpdir">dumped_output</parameter>
 </configuration>
 </testreport>
 <testreport type="html">
 <configuration>
 <parameter name="file">sample_report_xslt.html</parameter>
 <parameter name="dumpdir">dumped_output</parameter>
 </configuration>
 </testreport>
 </reporting>
 <tests>
 <testcase>
 <inputdocument>invoic_00256850.xml</inputdocument>
 <assertions>
 <content xpath="/INVOIC/SG_THEADER/S_STX/APRF" expect="INVTES">Invoice is test-only</content>
 </assertions>
 </testcase>
 </tests>
</testsuite>
The JCo connection to the SAP-XI server works yet the XSLT program is not recognized.
Has anybody experienced similar problems and found a solution?
Regards,
Uwe

Hello everybody,
I have the same problem, but as path delimiter I use the slash.
<parameter name="name">com/invoice01/my_map.xsl</parameter>
Detroubulator with option -d writes such a log:
1A "3" "Creating XSLT mapping /EDIFAKT/xslt/InvoiceEdiToInvoiceIdoc.xsl."
2A "3" "Load 0c04fdb5-57db-3510-989e-afa01a95280e, http://vng.de/xi/energy/vng, -1, EDIFAKT/xslt/InvoiceEdiToInvoiceIdoc.xsl."
3A "3" "Search EDIFAKT/xslt/InvoiceEdiToInvoiceIdoc.xsl (http://vng.de/xi/energy/vng, -1) in swcv 0c04fdb5-57db-3510-989e-afa01a95280e."
4A "3" "Does not found exact entry. Search in other namspaces."
5A "3" "Search EDIFAKT/xslt/InvoiceEdiToInvoiceIdoc.xsl (-1) in swcv 0c04fdb5-57db-3510-989e-afa01a95280e without namespace."
6A "1" "Unable to find resource EDIFAKT/xslt/InvoiceEdiToInvoiceIdoc.xsl (http://vng.de/xi/energy/vng, 0c04fdb5-57db-3510-989e-afa01a95280e, -1)"
7A "1" "com.sap.aii.ibrun.server.mapping.persist.ResourceNotFoundException: Unable to find resource EDIFAKT/xslt/InvoiceEdiToInvoiceIdoc.xsl (http://vng.de/xi/energy/vng, 0c04fdb5-57db-3510-989e-afa01a95280e, -1) at com.sap.aii.ibrun.server.mapping.persist.DBSwcvMappingPersistor.getInputStream(DBSwcvMappingPersistor.java:325) at com.sap.aii.ibrun.server.mapping.persist.DBSwcvMappingPersistor.readFile(DBSwcvMappingPersistor.java:203) at com.sap.aii.ibrun.server.mapping.MappingResolver.loadSource(MappingResolver.java:114) at com.sap.aii.ibrun.server.mapping.MappingPool$TemplateFactory.load(MappingPool.java:314) at com.sap.aii.ibrun.server.mapping.MappingPool$TemplateFactory.newFactory(MappingPool.java:331) at com.sap.aii.ibrun.server.mapping.pool.Pool.getNewPoolLine(Pool.java:72) at com.sap.aii.ibrun.server.mapping.pool.Pool.checkOut(Pool.java:60) at com.sap.aii.ibrun.server.mapping.MappingPool.checkOut(MappingPool.java:82) at com.sap.aii.ibrun.server.mapping.XSLTMapping.executeStep(XSLTMapping.java:44) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:92) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0_0.processFunction(MappingServiceObjectImpl0_0.java:131) at sun.reflect.GeneratedMethodAccessor277.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:62) at java.lang.reflect.Method.invoke(Method.java:391) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy217.processFunction(Unknown Source) at sun.reflect.GeneratedMethodAccessor276.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:62) at java.lang.reflect.Method.invoke(Method.java:391) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(AccessController.java:215) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)"
The xi system finds the xslt as part of a szenario.
Regards
Christof

Similar Messages

Error when loading XSLT mapping of the application

Hi,
I am using XSLT mapping in XI.
It is working ok when I test it in Interface Mapping but it gives below error when I test end to end scenario.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">TRANSFORMER_CONF_EX</SAP:Code>
<SAP:P1>com/cba/***.xsl</SAP:P1>
<SAP:P2>urn:**:**</SAP:P2>
<SAP:P3>450326d0-1559-11dd-99a1-d89c0a0a380b</SAP:P3>
<SAP:P4>-1</SAP:P4>
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error when loading XSLT mapping of the application</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Yes, I have activated it
Regards,
Anirudh.

hi
please assure that if you save your xslt stylesheet locally, that it is saved in UTF-8 format, before you import it.
Pls do export the imported archive as a zip file to your local disk and try opening the same. If its not then the zip file which you have uploaded might have got corrupted/is not fully uploaded.
Try activating the imported archive and do a check before you do that. This you can do with a minor change in the description or so.
reward points if found helpfull
regards
chandra.k

Problem when using XSLT Mapping with Java Methods.

<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:javamap="java:at.pi.mapping.besoldung.BesoldungMapping">
 <xsl:template match="Messages">
 <Messages>
 <Message1>
 <xsl:apply-templates></xsl:apply-templates>
 </Message1>
 </Messages>
 </xsl:template>
 <xsl:template match="Message1">
 <test></test>
 <xsl:param name="inputparam"></xsl:param>
 <xsl:for-each select="MT_BesoldungConversions">
 <test1></test1>
 
 <xsl:if test="function-available('javamap:createWhitespace')">
 <xsl:if test="function-available('javamap:extendTextWithWhitespaces')">
 <MT_BesoldungOut>
 <EDI_DC40>
 <xsl:param name="tablename">
 <xsl:value-of select="tablename"></xsl:value-of>
 </xsl:param>
 <xsl:variable name="constTen">10</xsl:variable>
 <xsl:value-of select="javamap:extendTextWithWhitespaces($tablename,$tablename, $inputparam)"></xsl:value-of>
 </EDI_DC40>
 </MT_BesoldungOut>
 </xsl:if>
 </xsl:if>
 </xsl:for-each>
 </xsl:template>
</xsl:stylesheet>

incomplete post

XSLT mapping not working b'coz " " & " " replaced with and

Hello Experts,
I have a RFC to JMS scenario. One of the parameter of RFC is a string field. This field will contain the XML data in it.
I need to create a complete XML payload using this data in a string field. For this I am using XSLT map :
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.1" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" >
 <xsl:output method="xml" omit-xml-declaration="no"/>
 <xsl:template match="/">
 <xsl:for-each select="//Nem">
 <xsl:copy-of select="."/>
 </xsl:for-each>
 </xsl:template>
</xsl:stylesheet>
This XSLT mapping works fine when tested independently.
But in actual scenario at runtime the "<" & ">" used to indicate a node are getting replaced with < and >. Then the XSLT mapping fails and produces no output.
The output of XSL will be passed in to a java mapping which signs the payload digitally.
What is the issue with these signs? How can I overcome this problem?
Any inputs will be of great help.
Kind Regards,
Abhijeet.
Edited by: Abhijeet Ambekar on May 4, 2010 2:01 PM

Hi Stefan,
Yes - I want to get rid of & # 60. But these (& # 60 and & # 62) are not added by XSLT mapping. Rather they are in the input available to XSLT map.
In sxmb_moni, i can see the inbound payload correctly :
<?xml version="1.0" encoding="UTF-8" ?>
- <rfc:HDK083_REFUS_SENDDOCU xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
<P_SIGN_DOCUMENT />
<P_XML_DOCUMENT><NemRefusionIndberetningSamling><NemRefusionIndberetningStruktur MessageID="1"><HeaderStruktur><SignOffIndikator>true</SignOffIndikator><TransaktionKode>Opret</TransaktionKode><IndberetningstypeKode>Anmeldelse</IndberetningstypeKode><FravaerTypeKode>Sygdom</FravaerTypeKode><FravaerendeStruktur><FravaerendeTypeKode>Loenmodtager</FravaerendeTypeKode><LoenUnderFravaerIndikator>false</LoenUnderFravaerIndikator></FravaerendeStruktur><IndberetningUUIDIdentifikator>bf9cc44e-af15-4e19-8457-5845d75385d2</IndberetningUUIDIdentifikator><ReferenceAttributTekst>ref. Nielsen-1503831372 (23. oktober 2009)</ReferenceAttributTekst>
but when I try to download the payload or right click on payload to view source I get something like below:
<?xml version="1.0" encoding="UTF-8"?><rfc:HDK083_REFUS_SENDDOCU xmlns:rfc="urn:sap-com:document:sap:rfc:functions"><P_SIGN_DOCUMENT></P_SIGN_DOCUMENT><P_XML_DOCUMENT>& # 6 0;NemRefusionIndberetningSamling& # 62; & # 60;NemRefusionIndberetningStruktur MessageID="1"& #62;& #60;HeaderStruktur& #62;& #60;SignOffIndikator& #62;true& #60;/SignOffIndikator& #62;& #60;TransaktionKode& #62;Opret& #60;/TransaktionKode& #62;& #60;IndberetningstypeKode& #62;Anmeldelse& #60;/IndberetningstypeKode& #62;& #60;FravaerTypeKode& #62;Sygdom& #60;/FravaerTypeKode& #62;& #60;FravaerendeStruktur& #62;& #60;FravaerendeTypeKode& #62;Loenmodtager</FravaerendeTypeKode><LoenUnderFravaerIndikator& #62;false</LoenUnderFravaerIndikator></FravaerendeStruktur& #62;<IndberetningUUIDIdentifikator& #62;bf9cc44e-af15-4e19-8457-5845d75385d2& #60;/IndberetningUUIDIdentifikator& #62;& #60;ReferenceAttributTekst& #62;ref. Nielsen-1503831372 (23. oktober 2009)& #60;/ReferenceAttributTekst& #62;
(extra spaces added to "& # 60" as browser was converting it to < ,>)
If i take the source code for payload and test XSLT mapping, it fails. But if I manually replace all "& # 60" with < and "& # 6 2" with >, then the mapping works fine.
So I think for XSLT map to work correctly, we need to replace all "& # 60 " . Please suggest.
Kind Regards,
Abhijeet.

Reg - XSLT Mapping using stylesheet exception during test

Hi experts,
I am new to SAP PI. Currently i am working on PI's XSLT Mapping using Stylusstudio.
I got error *Transformer Configuration Exception occurred when loading XSLT <name>.xsl; details: Could not compile stylesheet*.
I tried test by selecting SAP XML TOOLKIT too, then i am facing
*com.sap.engine.lib.xml.parser.NestedSAXParseException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: Prefix 'a' is not mapped to a namespace (:main:, row:4, col:15)(:main:, row=4, col=15) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: Prefix 'a' is not mapped to a namespace (:main:, row:4, col:15)*.
Kindly help me to overcome this issue.

Hi,
Simply your XSLT file is not a well-formed XML. Check your syntax. You could also use the XML Tools plugin to Notepad++ to help you determine where the syntax error is precisely.
Moreover, this error "Prefix 'a' is not mapped to a namespace" might mean that you are using a tag: <a:something>, but "a" is not properly declared as a namespace, for instance like: xmlns:a="something.sap.com".
Hope this helps,
Greg

XSLT Mapping, Transformer configuration exception occurred when loading

Hi,
My source message is an IDOC HRMD, I need my target message to include exactly
<EPERSON xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="ContextPersonMessage">
I have therefore suggested to use XSLT mapping.
Here is the test_mapping.xsl that I Imported as Zip in Imported Archives.
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:ns0="http://polyright.com/xi/HR">
 <xsl:template match="/">
 <EPERSON xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="ContextPersonMessage">
 <xsl:for-each select="HRMD_A07/IDOC/E1PLOGI">
 <CONTEXTPERSON personid="" id="">
 <PERSON action="add">
 <TITLE></TITLE>
 <FIRSTNAME><xsl:value-of select="E1PITYP/E1P0002/VORNA"/></FIRSTNAME>
 <SECONDNAME></SECONDNAME>
 <NAME><xsl:value-of select="E1PITYP/E1P0002/NACHN"/></NAME>
 <ADDRESS1></ADDRESS1>
 <ADDRESS2></ADDRESS2>
 <POSTALCODE></POSTALCODE>
 <CITY></CITY>
 <COUNTRY></COUNTRY>
 <COUNTRYID></COUNTRYID>
 <PROFESSION></PROFESSION>
 <LANGUAGE></LANGUAGE>
 <LANGUAGEID></LANGUAGEID>
 <PERSONTYPEID></PERSONTYPEID>
 <CREATIONDATE></CREATIONDATE>
 <BIRTHDATE></BIRTHDATE>
 <CATEGORY></CATEGORY>
 </PERSON>
 </xsl:for-each>
 </EPERSON>
 </xsl:template>
</xsl:stylesheet>
When I test the Interface mapping, I get the following error:
Transformer configuration exception occurred when loading XSLT test_mapping.xsl (http://polyright.com/xi/HR, 783938d1-4463-11dd-b136-e03ac0a80c15, -1)
Searching through the forum, it is probably an namespace issue, but I have no idea of what needs to be changed. Any suggestions ?

Try running end-to-end scenario and check if you could get detailed error message.
Also check if the problem arises from the "ns0" usage.
Regards,
Prateek

XSLT Mapping - problem with prefixes when calling template

Hi all,
I am having a problem with using an XSLT mapping in XI to combine various fields from 2 input messages of different structures into a single output message. I understand that XI puts a wrapper around the 2 input messages so the structure of the XML I am mapping is:
<?xml version="1.0" encoding="UTF-8"?>
<ns2:Messages xmlns:ns2="http://sap.com/xi/XI/SplitAndMerge">
<ns2:Message1>
<ns:(root of first message)>
</ns:(root of first message)>
</ns2:Message1>
<ns2:Message2>
<ns:(root of second message)>
</ns: (root of second message)>
</ns2:Message2>
</ns2:Messages>
Currently my XSL looks like the following:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:ns="http://example.co.uk/example" xmlns:ns2="http://sap.com/xi/XI/SplitAndMerge" xmlns:javamap="java:systemDate.CurrentDate" version="2.0">
<xsl:output method="xml" version="1.0" encoding="UTF-8"/>
<xsl:param name="inputparam"/>
<xsl:template match="ns2:Messages">
...<xsl:calltemplate name="FormattingTemplate"/>
</xsl:template>
<xsl:template name="FormattingTemplate">
</xsl:template>
</xsl:stylesheet>
When I test the mapping it works fine until it calls the FormattingTemplate. Then it throws out a "transformer exception" error saying the prefix 'ns2' is not mapped to a namespace.
If anyone could tell me where I am going wrong I would be very grateful.
Thanks,
Mike

Hi Udo,
Thanks for your reply.
When testing the stylesheet locally with XMLSpy, it works fine, but I have just noticed that it adds information in the root tag of the target message as follows:
<(root of target message) xmlns:javamap="java:systemDate.CurrentDate" xmlns:ns="http://example.co.uk/example" xmlns:ns2="http://sap.com/xi/XI/SplitAndMerge">
I checked the root tag of the target message in XI and it does not automatically add this information. Thus I added it in my stylesheet so the information above is projected in the target message, but the same error message appears when the call template function is called. Do you know if I need to somehow add a namespace to templates other than the main one? If so, do you know how I go about doing that?
Thanks,
Mike

Got Exceptions XSLT mapping while testing the scenarion.........

Hi
I got the following exceptions while testing the XSLT mapping scenario...
Hi
I have created a XSLT mapping with java conjunction... i have created a ZIP file and i have palced java class file, java file and xsl file in that ZIP file... I have imported this archive into imported archives... but when i am testing the application i got the follwoing exceptions
Details
com.sap.engine.services.ejb.exceptions.BaseRemoteException:
Exception in method transform.
at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0.transform(MapServiceRemoteObjectImpl0.java:182)
at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0p4_Skel.dispatch(MapServiceRemoteObjectImpl0p4_Skel.java:104)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native
Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.lang.UnsupportedClassVersionError:
DATEandTIME/Date_Time (Unsupported major.minor version
49.0)
at java.lang.ClassLoader.defineClass0(Native
Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
at java.lang.ClassLoader.defineClass(ClassLoader.java:448)
at com.sap.aii.ibrep.server.mapping.ibrun.RepMappingLoader.findClass(RepMappingLoader.java:175)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at com.sap.engine.lib.xsl.xpath.JLBLibrary.<init>(JLBLibrary.java:33)
at com.sap.engine.lib.xsl.xpath.LibraryManager.getFunction(LibraryManager.java:69)
at com.sap.engine.lib.xsl.xpath.functions.XFFunctionAvailable.execute(XFFunctionAvailable.java:24)
at com.sap.engine.lib.xsl.xpath.ETFunction.evaluate(ETFunction.java:110)
at com.sap.engine.lib.xsl.xpath.XPathProcessor.innerProcess(XPathProcessor.java:54)
at com.sap.engine.lib.xsl.xpath.XPathProcessor.process(XPathProcessor.java:41)
at com.sap.engine.lib.xsl.xpath.XPathProcessor.process(XPathProcessor.java:49)
at com.sap.engine.lib.xsl.xslt.XSLIf.process(XSLIf.java:28)
at com.sap.engine.lib.xsl.xslt.XSLNode.processFromFirst(XSLNode.java:293)
at com.sap.engine.lib.xsl.xslt.XSLElement.process(XSLElement.java:248)
at com.sap.engine.lib.xsl.xslt.XSLNode.processFromFirst(XSLNode.java:293)
at com.sap.engine.lib.xsl.xslt.XSLElement.process(XSLElement.java:248)
at com.sap.engine.lib.xsl.xslt.XSLNode.processFromFirst(XSLNode.java:293)
at com.sap.engine.lib.xsl.xslt.XSLTemplate.process(XSLTemplate.java:272)
at com.sap.engine.lib.xsl.xslt.XSLStylesheet.process(XSLStylesheet.java:457)
at com.sap.engine.lib.xsl.xslt.XSLStylesheet.process(XSLStylesheet.java:391)
at com.sap.engine.lib.jaxp.TransformerImpl.transformWithStylesheet(TransformerImpl.java:392)
at com.sap.engine.lib.jaxp.TransformerImpl.transform(TransformerImpl.java:234)
at com.sap.aii.ibrep.server.mapping.ibrun.RepMappingTransformer.transform(RepMappingTransformer.java:150)
at com.sap.aii.ibrep.server.mapping.ibrun.RepXSLTMapping.execute(RepXSLTMapping.java:81)
at com.sap.aii.ibrep.server.mapping.ibrun.RepMappingHandler.run(RepMappingHandler.java:80)
at com.sap.aii.ibrep.server.mapping.rt.MappingHandlerAdapter.run(MappingHandlerAdapter.java:107)
at com.sap.aii.ibrep.server.mapping.ServerMapService.transformInterfaceMapping(ServerMapService.java:127)
at com.sap.aii.ibrep.server.mapping.ServerMapService.transform(ServerMapService.java:104)
at com.sap.aii.ibrep.sbeans.mapping.MapServiceBean.transform(MapServiceBean.java:40)
at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0.transform(MapServiceRemoteObjectImpl0.java:131)
... 10 more
; nested exception is:
java.lang.UnsupportedClassVersionError:
DATEandTIME/Date_Time (Unsupported major.minor version
49.0)
com.sap.engine.services.ejb.exceptions.BaseRemoteException:
Exception in method transform.
at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0.transform(MapServiceRemoteObjectImpl0.java:182)
at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0p4_Skel.dispatch(MapServiceRemoteObjectImpl0p4_Skel.java:104)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native
Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.lang.UnsupportedClassVersionError:
DATEandTIME/Date_Time (Unsupported major.minor version
49.0)
at java.lang.ClassLoader.defineClass0(Native
Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
at java.lang.ClassLoader.defineClass(ClassLoader.java:448)
at com.sap.aii.ibrep.server.mapping.ibrun.RepMappingLoader.findClass(RepMappingLoader.java:175)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at com.sap.engine.lib.xsl.xpath.JLBLibrary.<init>(JLBLibrary.java:33)
at com.sap.engine.lib.xsl.xpath.LibraryManager.getFunction(LibraryManager.java:69)
at com.sap.engine.lib.xsl.xpath.functions.XFFunctionAvailable.execute(XFFunctionAvailable.java:24)
at com.sap.engine.lib.xsl.xpath.ETFunction.evaluate(ETFunction.java:110)
at com.sap.engine.lib.xsl.xpath.XPathProcessor.innerProcess(XPathProcessor.java:54)
at com.sap.engine.lib.xsl.xpath.XPathProcessor.process(XPathProcessor.java:41)
at com.sap.engine.lib.xsl.xpath.XPathProcessor.process(XPathProcessor.java:49)
at com.sap.engine.lib.xsl.xslt.XSLIf.process(XSLIf.java:28)
at com.sap.engine.lib.xsl.xslt.XSLNode.processFromFirst(XSLNode.java:293)
at com.sap.engine.lib.xsl.xslt.XSLElement.process(XSLElement.java:248)
at com.sap.engine.lib.xsl.xslt.XSLNode.processFromFirst(XSLNode.java:293)
at com.sap.engine.lib.xsl.xslt.XSLElement.process(XSLElement.java:248)
at com.sap.engine.lib.xsl.xslt.XSLNode.processFromFirst(XSLNode.java:293)
at com.sap.engine.lib.xsl.xslt.XSLTemplate.process(XSLTemplate.java:272)
at com.sap.engine.lib.xsl.xslt.XSLStylesheet.process(XSLStylesheet.java:457)
at com.sap.engine.lib.xsl.xslt.XSLStylesheet.process(XSLStylesheet.java:391)
at com.sap.engine.lib.jaxp.TransformerImpl.transformWithStylesheet(TransformerImpl.java:392)
at com.sap.engine.lib.jaxp.TransformerImpl.transform(TransformerImpl.java:234)
at com.sap.aii.ibrep.server.mapping.ibrun.RepMappingTransformer.transform(RepMappingTransformer.java:150)
at com.sap.aii.ibrep.server.mapping.ibrun.RepXSLTMapping.execute(RepXSLTMapping.java:81)
at com.sap.aii.ibrep.server.mapping.ibrun.RepMappingHandler.run(RepMappingHandler.java:80)
at com.sap.aii.ibrep.server.mapping.rt.MappingHandlerAdapter.run(MappingHandlerAdapter.java:107)
at com.sap.aii.ibrep.server.mapping.ServerMapService.transformInterfaceMapping(ServerMapService.java:127)
at com.sap.aii.ibrep.server.mapping.ServerMapService.transform(ServerMapService.java:104)
at com.sap.aii.ibrep.sbeans.mapping.MapServiceBean.transform(MapServiceBean.java:40)
at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0.transform(MapServiceRemoteObjectImpl0.java:131)
... 10 more
; nested exception is:
java.lang.UnsupportedClassVersionError:
DATEandTIME/Date_Time (Unsupported major.minor version
49.0)
Please help me....
Best Regards
Ravi Shankar B
Message was edited by: RaviShankar B

Hi
Following is my XSLT code
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="2.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:javamap="java:DATEandTIME.Date_Time">
 <xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/>
 <xsl:param name="inputparam" />
 <xsl:template match="/">
 <MT_TARGET>
 <date>
 <xsl:if test="function-available('javamap:getDateValue')">
 <xsl:value-of select="javamap:getDateValue($inputparam)"/> </xsl:if>
 </date>
 <time>
 <xsl:if test="function-available('javamap:getTimeValue')">
 <xsl:value-of select="javamap:getTimeValue($inputparam)"/> <xsl:value-of select="$test"/>
 </xsl:if>
 </time>
 <project>
 <xsl:value-of select= "//project"/>
 </project>
 </MT_TARGET>
 </xsl:template>
</xsl:stylesheet>
Following is my Java Code
package DATEandTIME;
import java.util.Map;
import com.sap.aii.mapping.api.AbstractTrace;
import com.sap.aii.mapping.api.StreamTransformationConstants;
import java.util.*;
import java.text.*;
public class Date_Time {
 private static AbstractTrace trace = null;
 public static String getDateValue(Map inputparam)
 trace = (AbstractTrace)inputparam.get(
 StreamTransformationConstants.MAPPING_TRACE );
 Date now1 = new Date();
 SimpleDateFormat formatter = new SimpleDateFormat ("yyyyMMd");
 String dateString = formatter.format(now1);
 return dateString;
 public static String getTimeValue(Map inputparam)
 trace = (AbstractTrace)inputparam.get(
 StreamTransformationConstants.MAPPING_TRACE );
 Date now1 = new Date();
 SimpleDateFormat formatter = new SimpleDateFormat ("hhmmss");
 String dateString1 = formatter.format(now1);
 return dateString1;
Best Regards
Ravi Shankar B

How to perform an XSLT Mapping Test

Hi,
I have defined an XSLT Mapping in XI and it seems to work, but when I perform a test in my Interface Mapping the source fields are not written on respective target fields. What is the problem?
Thanks!

The issue is in the logic f your XSL mapping.
Use the same source XML and use it with XML Spy to debug why it is not working as you want it to.
Regards
Bhavesh

Xsi:nil="true" in XSLT Map breaks "choose"-"when" loops - annoying

Hello,
Handling "nil" element in choose loops breaks my XSLT tranformation.
As soon as the element is set to nil, either the "otherwise" branch is executed (wrongly) or the XSLT processing stops.
I test with "count" for the existence of the element. Depending on if it is nil,
other elements have to be processed in sub-loops.
I have an XSLT Mapping in JDeveloper.
It processes a SOAP request in the form:
<result>
<customerNew>CUSTOMER_NEW_NAME</customerNew>
<customerCurrent>CUSTOMER_NAME</customerCurrent>
</result>
which can also be:
<result>
<customerNew xsi:nil="true">
</customerNew>
<customerCurrent>CUSTOMER_NAME</customerCurrent>
</result>
To check for Nil I use:
<xsl:when test='not(boolean(count(/ns0:changeCustomer/result/customerNew))) and contains(/ns0:changeCustomer/result/customer,"USER_NAME_SOME_BODY")'>
(the xslt maps between two xsd files and we have quite strict schema definitions)
As soon as I use the test statement in a loop, it breaks, even if I test for "true" and do not simply check for count<1 etc.
How can I work with the <customerCurrent> Element, even if the previous element is nilled?
I talked to several experienced developers and nobody could help. They can do checks in plain xsl with xalan, but not in JDeveloper.
This took me five days already...who can advice?
Your help is appreciated very much.

hi user570144
You write "They can do checks in plain xsl with xalan, but not in JDeveloper.". Could you describe in detail what it is you (would like to) do "in JDeveloper" and how that is different from "plain xsl with xalan"?
The "contains" function in your xsl:when test example has the expression "/ns0:changeCustomer/result/customer", but in the xml examples you gave there is no "customer" element inside the "result" element, only "customerNew" and "customerCurrent" elements.
(tip : You can use "Your Control Panel" to make your name visible in forum posts.)
regards
Jan Vervecken

Error in XSLT Mapping when special character is passed through

Hi Experts,
We have used the XSLT mapping. When ever any special character like é is being passed, then the below mentioned error is displayed in the Integration engine.
Error occurred during XSLT mapping of the application
It is working fine with normal case if we are not sending any special character.
I am not sure whether the problem exists in XSLT mapping or the issue with the legacy system?
Early response would be highly appreciated and points will be awarded.
Thanks in Advance,
Jitender

hi,
[Problem in transforming XML to string using XSLT;
Chk the above link.might solve ur issue.
Regards.
Siddhesh Naik

XSLT MAPPING TEST PROBLEM

Hi All,
We had a problem while testing mapping in Altova Map Force.Here question is while testing our mapping in IR's interface mapping we got the message "Error while loading XSLT ".Target result is notgetting displayed.
Any ideas.....
Regards,
Surya.

After importing XSL in imported archives, double click it and check whether u can open it or not. Make sure that the namespace ur XSL uses is same as the namespac under which it is imported. Make sure file loaded is XSL and not XSLT. Then try running end-to-end scenario and check the result.
Regards,
Prateek

Getting Java mapping errors when testing my Interface mapping

Hi,
I'm trying to test my interface mapping from IR, I keep getting these exceptions. All I'm doing in my interface mapping is I have two mapping programs a XSLT mapping with java helper functions with the XSL and a message mapping. In the test it pass thru the XSLT mapping but fails at Message mapping and throws the following exception. Any help on this is really appreciated.
10:03:26 Start of test
Call XSLT processor with stylsheet com/earthlink/xi/mapping/xmlc_to_crm_resp.xsl.
START APPLICATION TRACE ***
Response:
0
END APPLICATION TRACE ***
Returned form XSLT processor.
Call method execute of the application Java mapping com.sap.xi.tf._MM_XMLC_RESP_
Error during appliction Java mapping com/sap/xi/tf/_MM_XMLC_RESP_
java.lang.NullPointerException at com.sap.aii.mappingtool.tf3.AMappingProgram.exceptionCaught$(AMappingProgram.java:59) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:182) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:149) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrep.server.mapping.ibrun.RepJavaMapping.execute(RepJavaMapping.java:73) at com.sap.aii.ibrep.server.mapping.ibrun.RepSequenceMapping.execute(RepSequenceMapping.java:54) at com.sap.aii.ibrep.server.mapping.ibrun.RepMappingHandler.run(RepMappingHandler.java:80) at com.sap.aii.ibrep.server.mapping.rt.MappingHandlerAdapter.run(MappingHandlerAdapter.java:107) at com.sap.aii.ibrep.server.mapping.ServerMapService.transformInterfaceMapping(ServerMapService.java:127) at com.sap.aii.ibrep.server.mapping.ServerMapService.transform(ServerMapService.java:104) at com.sap.aii.ibrep.sbeans.mapping.MapServiceBean.transform(MapServiceBean.java:40) at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0.transform(MapServiceRemoteObjectImpl0.java:167) at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0p4_Skel.dispatch(MapServiceRemoteObjectImpl0p4_Skel.java:104) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320) at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198) at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
10:03:26 End of test

Joe,
most likely your XSLT is outputting a not well-formed XML message.
Remove message mapping from the mapping list and execute it again, to check output.
Also, for mapping debugging in java enhanced function inside XSLT mappings, use the following:
1st, you need to pass the "inputparam" parameter from the XSLT runtime to the Java function (it needs to be one of the input parameters for the executed java function).
In the Java code itself, implement the following code:
AbstractTrace trace = (AbstractTrace) param.get(StreamTransformationConstants.MAPPING_TRACE);
trace.addInfo("Log your message here!");
where param is the input parameter refering to the inputparam from XSLT.
The AbstractTrace and StreamTransformationConstants classes can be found in the aii_map_api.jar file (used in Java mappings).
Regards,
Henrique.

When I am testing java map in XI.every time connection to the XIserver lost

Hi All,
When I am testing java map in XI.every time connection to the XI server lost.XI is asking for login again
Can any one help me on this.what could be the problem
Thanks
Siree

I dont no whether problem with java code or XI .but its a very simple java code.
Just i am getting 6 Xpath values and comparing those values with "" OR Null.if the condition is true i am displaying some text message.
Sample Code
execute(in,out)
Xpath1
Xpath2
if("".equls(Xpath1)||Xpath1==null)
Textmessage = No value in Xpath1

SPROXY: XSLT Type Error when testing

We are using SAP PI 7.1 to consume ABAP Proxies. We have performed all the necessary configurations and are able to see the ESR from within SAP R/3. When testing an ABAP Proxy via SPROXYI receive the error shown below. In fact I receive this error for all proxies that I try to test, including standard SAP functions. I am assuming this is a configuration issue rather than a specific issue with a proxy. I have checked SDN and SAP Service and I can't find any mention of this specific error. Is there anyone out there who can help?
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIProxy</SAP:Category>
<SAP:Code area="ABAP">PARSE_APPLICATION_DATA</SAP:Code>
<SAP:P1>Request Message</SAP:P1>
<SAP:P2>CX_CALL_ST_ERROR</SAP:P2>
<SAP:P3 />
<SAP:P4>Error Text: A type conflict occurred during the parameter transfer to the root INPUT of /1SAI/TXS1EF71A636AE519CFE80A Kernel ErrorId: UNCAUGHT_EXCEPTION</SAP:P4>
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error during XML => ABAP conversion (Request Message; error ID: CX_CALL_ST_ERROR; ( Error Text: A type conflict occurred during the parameter transfer to the root INPUT of /1SAI/TXS1EF71A636AE519CFE80A Kernel ErrorId: UNCAUGHT_EXCEPTION)) A type conflict occurred during the parameter transfer to the root INPUT of /1SAI/TXS1EF71A636AE519CFE80A</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>

Hi Robert,
i know that this is quite late. The problem is with the XSLT which gets generated when you generate PROXY. And some times the kernel doesn't doesn't set the conversion of XSLT correctly. you can check the syntax of the XSLT /1SAI/TXS1EF71A636AE519CFE80A in the transaction STRANS.
There should be some basis notes from the component BC-DWB-PRX to solve the problem.

Detroubulator: RESOURCE_NOT_FOUND when testing XSLT mapping

Similar Messages

Maybe you are looking for