CDATA - XSLT mappping - Encoding problem

Hi folks,
I have a ABAP proxy to webservice scenario...
I am sending out data from ECC to a external web service...
The requirement here is the external web service input message has only two input fields and in the first field it accepts the transaction data( Say material or customer or orders ect) and in the second field it accepts login aunthetication information which is generally fixed..
<ObjectsDataXml>
<![CDATA[ mat1......mat2.....mat3....matn]]>
</ObjectsDataXml>
<UserContextXml>
<![CDATA[ login infomration ]]>
</UserContextXml>
The requirement here is all the data records are bundled into and put into <objectDataXml> tag with in CDATA..
same to do with <UserContextXml> as shown above..
In my operation mapping am using message mapping to map material records to the target structure and then using XSLT map to put all the data in to CDATA and send it into the <ObjectsDataXml> tag...
Although the mapping working fine but the message output is having encoded values by the time message reaches adapter message content and external web service request..
I have tested the same in TCP gateway tool and i find two issues
1) The out is encoded for opeing and closing tags between CDATA and
2) CDATA is completely ignored....
Please find the link to have a look at the data after mapping and adapter call below
Output after Message mapping before calling the adapter:-
http://www.flickr.com/photos/62088318@N08/5641894710/
Output in the TCP gate way tool or external receiver:-
http://www.flickr.com/photos/62088318@N08/5641887100/
Please guide me with this.
Regards,
MrMarri

I recommend to change the web service. This is such a nonsense to use cdata section in a web service.
I do not understand and do not have any comprehensin for people who think that they can ignore any rule for creating web service.
The best proof of imcompetence is the use of namespace "tempuri.org" .
Sorry for being rude. I see a lot of questions here in SDN from people in PI who try to solve the issues which are made from sender or receiver systems.

Similar Messages

Generating CDATA containing XML-like text using XSLT Mapper in OFM 11g

Hi,
One of our partners requires XML to be sent as XML string inside a CDATA section. The use of "real" XML is not an option at the moment. We try to generate something like the following using XSLT/XSLT Mapper in SOA Suite 11g:
<element>
<![CDATA[
<supplierElement1>
<supplierElement2>
etcetera
<supplierElement2>
</supplierElement1>
]]>
</element>
We've tried the following two approaches, so far unsuccessful:
<xsl:template match="/">
<inp1:singleString>
<inp1:input>
<xsl:text disable-output-escaping="yes"><![CDATA[test]]></xsl:text>
</inp1:input
</inp1:singleString>
</xsl:template>
resulting in:
<inp1:singleString xmlns:inp1="http://xmlns.oracle.com/singleString">
<inp1:input><![CDATA[test]]></inp1:input>
</inp1:singleString>
and:
<xsl:output method="xml" indent="yes" cdata-section-elements="input"/>
<xsl:template match="/">
<inp1:singleString>
<input>test</input>
</inp1:singleString>
</xsl:template>
resulting in:
<inp1:singleString xmlns:inp1="http://xmlns.oracle.com/singleString" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<input>test</input>
</inp1:singleString>
Does anyone know how to generate the CDATA section declaratively (within XSLT/XSLT Mapper), without resorting to custom code and parsing as we have to do now?
Thanks!
Ronald

The exact error message I'm getting is :
ABAP XML formatting error in XML node of type "element", name: "abap"

Character encoding problem using XSLT and Tomcat on Linux

Hi,
I have an application running on a Tomcat 4.1.18 application server that applies XSLT transformations to DOM objects using standard calls to javax.xml.transform API. The JDK is J2SE 1.4.1_01.
It is all OK while running on a development enviroment (which is Windows NT 4.0 work station), but when I put it in the production enviroment (which is a red hat linux 8.0), it comes up with some kind of encoding problem: the extended characters (in spanish) are not shown as they should.
The XSL stylesheets are using the ISO-8859-1 encoding, but I have also tried with UTF-8.
These stylesheets are dynamicly generated from a JSP:
// opens a connection to a JSP that generates the XSL
URLConnection urlConn = (new URL( xxxxxx )).openConnection();
Reader readerJsp = new BufferedReader(new InputStreamReader( urlConn.getInputStream() ));
// Gets the object that represents the XSL
Templates translet = tFactory.newTemplates( new StreamSource( readerJsp ));
Transformer transformer = translet.newTransformer();
// applies transformations
// the output is sent to the HttpServletResponse's outputStream object
transformer.transform(myDOMObject, new StreamResult(response.getOutputStream()) );Any help would be appreciated.

Probably you need to set your LANG OS especific environment variable to spanish.
Try adding this line:
export LANG=es_ES
to your tomcat/bin/catalina.sh, and restart tomcat.
It should look like this:
# OS specific support. $var _must_ be set to either true or false.
cygwin=false
case "`uname`" in
CYGWIN*) cygwin=true;;
esac
export LANG=es_ES
# resolve links - $0 may be a softlink
PRG="$0"
.(BTW, keep using ISO-8859-1 encoding for your XSL)
HTH
Un Saludo!

XSLT Mapper: a lot of unused import namespaces

Hi.
The only way I have found to substitute an "any" element with a particular one from other schema in the XSLT mapper is to import the schemas in the main one. The problem is when you import a lot of schemas, the result mapper defines all these namespaces at the root level of the xslt (just in case), whether they are used or not. That produces an unnecessary overhead in the xslt file size.
Is there any way to clean up the result mapper, so only the needed namespaces will be defined?
It could seem it is not very important, but now I have 150 namespaces defined, when only 7 are used.
Thanks.
Ramon
Edited by: Ramon Gordillo on Jun 6, 2011 5:19 PM

Hi.
I have been watching for some solutions, like for example the wtp for eclipse, which allows you to select the namespaces and clean them manually (without further checks than a valid XML), but all of the solutions falls in the "select" expressions with xpaths referring namespaces (and some of them, also with QNames elements).
Any help? Oracle masters?

XSLT Mapper doesn't support xsi:type

I'm starting to think that XSLT Mapper supports only the basic features of XML Schema ...
It (XSLT Mapper in JDeveloper) does not seem to support mapping to generate this kind of element (cannot do it in Design view, when added to the Source view, cannot go back to Design view):
<HighLevel:ParentEntity xsi:type="HighLevel:AChildEntity" xmlns:HighLevel="someNamespace">
<A>ABC</A>
<B>1</B>
<FromAChildEntity>ABCDE</FromAChildEntity>
</HighLevel:ParentEntity>
If we leave this in Source view and run the xsl, the resulting XML has a validation error, the last element (FromAChildEntity is not known). The XML is valid in XML Spy.
This problem combines with not being able to map two source elements to one target element, makes XSLT Mapper not able to deal with XML Schema inheritance at all.... ?

I just want to reformat the XML from the original message (didn't realize I had to escape some of the characters). This is the XML that cannot be validated by JDeveloper):
<HighLevel:ParentEntity xsi:type="HighLevel:AChildEntity" xmlns:HighLevel="someNamespace">
<A>ABC</A>
<B>1</B>
<FromAChildEntity>ABCDE</FromAChildEntity>
</HighLevel:ParentEntity>

Where is XSLT mapper?

I was advised by PeopleSoft Tech Support (who now work for Oracle!) that JDeveloper contained a utility for creating XSLT. There directions were to right-click the project, expand General, select XML, then select XSLT mapper in the Items list. Problem: XSLT mapper is NOT in that list, and I did not leave anything out when installing (Studio 10.1.3.0.3.3412)
Essentially I have an XML interface file that I generate out of PeopleSoft Financials - and I have an XML file that my non-PS client wants to receive. There is a gap between - ok, a chasm - and apparently this XSLT mapper enables you to drag a field from one file into the other & it will generate the XSLT code for you.
Can anyone shed some light on where this tool is? Thanks!

Paul, this is not in the EA1 realese of JDeveloper 10.1.3.
Something like this is suppose to be part of the BPEL extension to JDeveloper 10.1.3 production.
There are other "more manual" XSLT capabilities in JDeveloper right now.
See here:
http://www.oracle.com/technology/products/jdev/101/viewlets/101/xsltdebug_viewlet_swf.html

Encoding problems in email while on Windows Mail app

Hello.
I have a question concerning email and encoding problems in the Windows Mail App in Windows 8.1. I have encountered a problem with an email I received, while reading, I see strange ASCII characters in one email. I have never encountered it in
my web browsers nor Gmail, just the Mail App.
I was referred to come here when I had asked a similar question there:
http://answers.microsoft.com/en-us/windows/forum/windows8_1-ecoms/strange-foreign-ascii-characters-appearing-in/911f8a44-c302-4fa1-bcaa-3297b32d9120
I don't know which forum to go to so I picked here.
Is there any way that it can be resolved. I tried to troubleshoot, nothing worked; I even synched, to no avail.
I look forward to a response.
JB

Hi JB,
The responder on answers was a bit confused. The MSDN forums are for developers to discuss writing their own apps. We cannot help with problems using Windows or its built-in apps.
If the folks on answers cannot help then you may need to open a support incident. See
http://support.microsoft.com , or the folks on answers may be able to direct you to the specific page for the Windows Mail app.
--Rob

XSLT Mapper file does not open in design view

XSLT mapper file in the composites exported from weblogic EM as a jar and imported in JDeveloper 11.1.14 does not open in design view. There is no option of design view itself in the tab structure. It is viewable only in source view.
Please suggest, how do I view the desgn view of the xslt mapper?
Thanks,
Promiit

When you export composites from Weblogic EM in jar format, the resulting files are differently formatted from what was used for deployment.
So, basically, the XSLT file, you are trying to open in Jdeveloper has lost the "mapSources" and "mapTargets" sections, which are generally present in the header section of the jdeveloper-generated XSLT file. Try to manually hand-crack those sections and you should be good to go.
Hope it helps !

How to do closing tag: tag /tag instead of tag/ in jdev xslt mapper

Hi!
We have commercial systems, which cannot work with short closing tags for empty nodes.
Xslt mapper for oracle mediator optimize everytime to short closing tag, when node content is empty.
Is there a property or technique to achieve long closing tags?
Kind regards
Torsten

http://www.biglist.com/lists/xsl-list/archives/200610/msg00342.html
not really a pretty solution, but you could try adding the comments

How to use xslt mapper with sequence occurences

I'm using Bpel process manager.
I'm trying to use multiple partname fields in my xsd. I'have defined a sequence occurence in my xsd.
In the xslt mapper I see just one partname. How can I map initials, nickname, fullname etc to the 'different' partnames while I just see one.
I'hope somebody can help me?
Jasper Goede

I use the following xsd (just part of the whole xsd):
<xsd:complexType name="nameType">
<xsd:sequence>
     <xsd:element name="partname" type="partnameType" minOccurs="3" maxOccurs="5"/>
     </xsd:sequence>
     </xsd:complexType>
     <xsd:complexType name="partnameType">
     <xsd:sequence>
     <xsd:element name="typename" type="typenamenameType"/>
     <xsd:element name="text" type="nametextType"/>
     </xsd:sequence>
     </xsd:complexType>
In the xslt mapper I just see one text field. So I can connect only nickname to the text field. I suspect more text fields.

Disabling validation in xslt mapper

My xslt source code is valid as per xslt 1.0 and runs correctly when deployed. But the design view of the xslt mapper throws errors. How can I disable the error-checking of the xslt mapper?
Thanks,
Bipin Raj
PS:
Below is the xslt code that I added to my map, followed by the errors I am getting.
<ns0:NOTES>
<xsl:attribute name="index">
<xsl:value-of select='string("1")'/>
</xsl:attribute>
<xsl:for-each select="ns1:Loop-N9_1/ns1:Segment-N9">
<xsl:value-of select="ns1:Element-369"/>
<xsl:text>|</xsl:text>
</xsl:for-each>
<xsl:for-each select="ns1:Loop-N9_1/ns1:Segment-MSG">
<xsl:value-of select="ns1:Element-933"/>
<xsl:if test="position() != last()">
<xsl:text>|</xsl:text>
</xsl:if>
</xsl:for-each>
</ns0:NOTES>
Errors:
Error: Invalid Usage of <for-each> Element
Error: xsl:for-each does not Support Mixed Content
Error: xsl:for-each does not Support Mixed Content
Error: Invalid Usage of <for-each> Element
Error: Invalid Usage of <if> Element
Error: xsl:for-each does not Support Mixed Content
Error: xsl:for-each does not Support Mixed Content
Error: This Node is Already Mapped : "/ns0:PROCESS_PO_007/ns0:DATAAREA/ns0:PROCESS_PO/for-each"
Invalid Source Node Path (//ns1:Transaction-850/ns1:Loop-PO1/ns1:Element-933)
Invalid Source Node Path (//ns1:Transaction-850/ns1:Loop-PO1/ns1:Element-369)

Can you explain a bit more what you want to do. It's very vague right now. Probably will be able to help you out.
Thanks

How to use xslt mapper

I'have created a xsd with sequence occurences. In the xslt mapper I try to connect nickname, initials and full name to the same field, because I just see one field.
Can somebody help me?
Thanks
Jasper

I use the following xsd (just part of the whole xsd):
<xsd:complexType name="nameType">
<xsd:sequence>
     <xsd:element name="partname" type="partnameType" minOccurs="3" maxOccurs="5"/>
     </xsd:sequence>
     </xsd:complexType>
     <xsd:complexType name="partnameType">
     <xsd:sequence>
     <xsd:element name="typename" type="typenamenameType"/>
     <xsd:element name="text" type="nametextType"/>
     </xsd:sequence>
     </xsd:complexType>
In the xslt mapper I just see one text field. So I can connect only nickname to the text field. I suspect more text fields.

Can not find xslt mapper

Hi ,
I need to use the xslt mapper to transform the xml from site A to the xml structure that site B can accept. The documents mention that the xslt mapper is the new featrue for JDeveloper. I download the 11GR2 from Oracle and can not find the tool in it. Some posts said that it is the feature in 10G and then i continue to download the 10G JDV but i can not find this tool also.
Does anyone use this feature and can give me some suggestions?
Thanks in advance.

goto the project properties.. Run/ Debugs Profile -> Default - Edit -> Launch Settngs [XSLT]
here provide input and output xml file..
if you want a visual transformation then you have to use.. SOA Suite.. BPEL
http://download.oracle.com/docs/cd/E12483_01/integrate.1013/b28981/xslt_mpr.htm

XSLT Mapper - Transform - Error when using remote WSDL/XSD

Whenever I attempt to use JDeveloper built in XSLT Mapper on a remote WSDL service the mapper either gives me a blank mapper screen or throws a error.
But when I pull the WSDLS and the XSDs into JDeveloper and use those for my Partner links the mapper does not have any issues.
The WSDLS and XSDs are being generated by Weblogic 10.3 and the SOA version I'm using is 11g. Everything is the newest download of 11g as of about 3 days ago.
Is there a known issue with the XSLT mapper or am I doing something wrong?
If you need any other information just ask thank you.

The XSLT service is configurable.
http://help.adobe.com/en_US/LiveCycle/9.5/WorkbenchHelp/WS92d06802c76abadb-1cc35bda128261a 20dd-6750.html
1) Stop LiveCycle.
2) Add the .jars of your XSLT processor of choice to the LiveCycle server lib folder.
3) Restart LiveCycle.
4) Go to Workbench and stop the XSLT service. Right-click on XSLTService:1.0 and Edit Service Configuration.
5) Enter the factory name for the given XSLT processor. I think for Xalan 2.7.1 it is org.apache.xalan.processor.TransformerFactoryImpl (but I could be wrong).
6) Restart the service.
Steve

Encoding problem while reading binary data from MQ-series

Dear all,
we are running on 7.0 and we have an encoding problem while reading binary data from MQ-series. Because we are getting flat strings from queue we use module "Plain2ML" (MessageTransformBean) for wrapping xml-elements around the incoming data.
The MQ-Series-Server is using CCSID 850, which we configured in connection parameters in communication channel (both parameters for Queuemanager CCSID and also CCSID of target).If there are special characters in the message (which HEX-values differ from codepage to codepage) we get errors in our adapter while executing, please see stack-trace for further analysis below.
It seems to us that
1. method ByteToCharUTF8.convert() expects UTF-8 in binary data
2. Both CCSID parameters are not used anyway in JMS-adapter
How can we solve this problem without changing anything on MQ-site?
Here is the stack-trace:
Catching com.sap.aii.af.mp.module.ModuleException: Transform: failed to execute the transformation: com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'sun.io.MalformedInputException'; nested exception caused by: sun.io.MalformedInputException caused by: com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'sun.io.MalformedInputException'; nested exception caused by: sun.io.MalformedInputException
    at com.sap.aii.af.modules.trans.MessageTransformBean.throwModuleException(MessageTransformBean.java:453)
    at com.sap.aii.af.modules.trans.MessageTransformBean.process(MessageTransformBean.java:387)
    at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_0.process(ModuleLocalLocalObjectImpl0_0.java:103)
    at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:292)
    at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0_0.process(ModuleProcessorLocalLocalObjectImpl0_0.java:103)
    at com.sap.aii.adapter.jms.core.channel.filter.SendToModuleProcessorFilter.filter(SendToModuleProcessorFilter.java:84)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.ConvertBinaryToXiMessageFilter.filter(ConvertBinaryToXiMessageFilter.java:304)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.ConvertJmsMessageToBinaryFilter.filter(ConvertJmsMessageToBinaryFilter.java:112)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.InboundDuplicateCheckFilter.filter(InboundDuplicateCheckFilter.java:87)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.TxManagerFilter.filterSend(TxManagerFilter.java:123)
    at com.sap.aii.adapter.jms.core.channel.filter.TxManagerFilter.filter(TxManagerFilter.java:59)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.DynamicConfigurationFilter.filter(DynamicConfigurationFilter.java:72)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.PmiAgentFilter.filter(PmiAgentFilter.java:66)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.InboundCorrelationFilter.filter(InboundCorrelationFilter.java:60)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.JmsHeadersProfileFilter.filter(JmsHeadersProfileFilter.java:59)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageInvocationsFilter.filter(MessageInvocationsFilter.java:89)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.JarmMonitorFilter.filter(JarmMonitorFilter.java:57)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.ThreadNamingFilter.filter(ThreadNamingFilter.java:62)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.SenderChannelImpl.doReceive(SenderChannelImpl.java:263)
    at com.sap.aii.adapter.jms.core.channel.ChannelImpl.receive(ChannelImpl.java:437)
    at com.sap.aii.adapter.jms.core.connector.MessageListenerImpl.onMessage(MessageListenerImpl.java:36)
    at com.ibm.mq.jms.MQMessageConsumer$FacadeMessageListener.onMessage(MQMessageConsumer.java:399)
    at com.ibm.msg.client.jms.internal.JmsMessageConsumerImpl$JmsProviderMessageListener.onMessage(JmsMessageConsumerImpl.java:904)
    at com.ibm.msg.client.wmq.v6.jms.internal.MQMessageConsumer.receiveAsync(MQMessageConsumer.java:4249)
    at com.ibm.msg.client.wmq.v6.jms.internal.SessionAsyncHelper.run(SessionAsyncHelper.java:537)
    at java.lang.Thread.run(Thread.java:770)
Caused by: com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'sun.io.MalformedInputException'; nested exception caused by: sun.io.MalformedInputException
    at com.sap.aii.messaging.adapter.Conversion.service(Conversion.java:714)
    at com.sap.aii.af.modules.trans.MessageTransformBean.processTransform(MessageTransformBean.java:538)
    at com.sap.aii.af.modules.trans.MessageTransformBean.processTransform(MessageTransformBean.java:528)
    at com.sap.aii.af.modules.trans.MessageTransformBean.processTransform(MessageTransformBean.java:471)
    at com.sap.aii.af.modules.trans.MessageTransformBean.process(MessageTransformBean.java:364)
    ... 36 more
Caused by: sun.io.MalformedInputException
    at sun.io.ByteToCharUTF8.convert(ByteToCharUTF8.java:270)
    at sun.nio.cs.StreamDecoder$ConverterSD.convertInto(StreamDecoder.java:287)
    at sun.nio.cs.StreamDecoder$ConverterSD.implRead(StreamDecoder.java:337)
    at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:223)
    at java.io.InputStreamReader.read(InputStreamReader.java:208)
    at java.io.BufferedReader.fill(BufferedReader.java:153)
    at java.io.BufferedReader.readLine(BufferedReader.java:316)
    at java.io.LineNumberReader.readLine(LineNumberReader.java:176)
    at com.sap.aii.messaging.adapter.Conversion.convertPlain2XML(Conversion.java:310)
    at com.sap.aii.messaging.adapter.Conversion.service(Conversion.java:709)
    ... 40 more
Any ideas?
Kind regards, Stefan

Hi Stefan,
for the first MTB now we are using only one parameter: Transform.ContentType = text/plain;charset="ISO-8859-1"
The second MTB, which does the XML-Wrapping, is configured like this:
Transform.Class = com.sap.aii.messaging.adapter.Conversion
Transform.ContentType = application/xml
xml.conversionType = SimplePlain2XML
xml.fieldNames = value
xml.fieldSeparator = §%zulu§%
xml.processFieldNames = fromConfiguration
xml.structureTitle = payload
Both CCSID configuration parameters from the "Source"-Tab we've set to 850.
Now, we don't get an error anymore - sun.io.malformedInputException - , but, unfortunately, now special character conversion succeeded (we need an "ß" and we get an ISO-HEX-E1 -> á). E1 is (different from ISO) an "ß" in 850.
Any ideas?

CDATA - XSLT mappping - Encoding problem

Similar Messages

Maybe you are looking for