Non xml char

Hi, all,
I need to create a DOM tree and take the value from user input,
I have no idea how the user can enter the strange chars like BEL.
Do I need validate every char make sure is in the xml char range when I create
the node? or the biuld in parser will take care of it?

Hi,
use
out.write(OutputDoc.asXML().getBytes("UTF-8"));
or
out.write(OutputDoc.asXML().getBytes("ISO-8559-1"));
Regards, mario

Similar Messages

Map binary data (PDF) to XML not possible due to non-printable chars

Hi XI Gurus,
we have the following issue.
We send a PDF as binary data (as a hex string '25255044462D3' ) along with some other information from ERP within one RFC to XI , doing a message split 1:n for those two kind of messages (1. the PDF, 2. the XML) an send the split messages to file/ftp receiver adapter.
The message split and sending of the messages is working well, but we encounter some problems with non-printable chars (hex code below 0x20) in the pdf binary. The PDF data and the dynamic file name is mapped into an XML. But the non printable characters are converted into '#' when mapped into the XML target field.
(Due to the 1:n multi mapping, we cannot put the filename into dynamic configuration, so we have to map the pdf and the filename into an XML and extract the content with variable substitution in receiver file adapter....)
My question is: how can binary data with non-printable chars be sent through XI and can be mapped into an XML without beeing replaced by '#' ?
Any help will be greatly appreciated.
Thanks and regards
Holger

Maybe I didn´t explained it clearly enough.
We do not have the issue that the RFC puts the '#' into the string. We got from the RFC a hex string containing the pdf as visible hex values like:
As you can see we have the pdf as hex string. During message mapping XI replaces some non-printable chars like '0x04' or '0x19' with '#'.
My question is: how can we avoid those char replacement ?
BTW: I grabbed a pdf with sender file adapter, routed through XI without any mapping and send it with ftp in binary mode. But the pdf contains more chars as the origional file and the pdf content is not visible when opening with a pdf reader like Acrobat. I guess the file adpter has problems with carriage return and linefeed chars. Some CR and LF are replaced inserted somehow.
Best regards,
Holger

Select xmlelement of clob containing non-printable chars gives ORA-31011

Using sqlplus against Ora9i database. We have some rows where the CLOB column contains non-printable chars because of a conversion from an old system.
I'm trying to extract this data using xmlselect. Most of the time it works great, but for the above rows it dies with error:
ORA-31011: XML parsing failed
If I embed substr(columname,1,25) so that it doesn't get to the non-printable character (which is at about position 200), then the sql works great.
Any ideas on how to massage this data, either on the fly, or I could do a one-time conversion. The problem is that darn CLOB. I can't even figure out how to find all the bad rows. Looking for sql to find the bad rows, or a function that I could put in a package, and then call from the select to convert it on the fly.
thanks,
Rick

Thanks for your help. Anything I do (including your suggestion) to try and parse the xml bombs with an internal error. Without raising the exception.
What I decided to do instead is do a search in the clob using instr(column, CHR(13)) but for also all CHR that are less than 32. I then replace it with a space. So I'm going to fix the data once rather than doing an on the fly fix.
thanks again,
Rick

Non XML attachment to XML in sender mail adapter

Hi,
I am working with sender mail adapter and usng payloadswapbean. My attachment is non XML and I need to convert it in to XML in order to mapping. How can I do that? Can someone explain if can I use MessageTransformBean for this purpose and if so, how?
Or any other method for doing this?
Thanks,
Rakesh

Is the attachment in text format? If yes, then after the usage of PayloadSwapBean, you may try using MessageTransformBean in the same module chain. And you will be able to convert it into xml format.
Regards,
Prateek

How to add exactly 2 NON XML caracters at the end of a SOAP body

Hello all I am trying to add two (and only two) extra non xml caracters "AA" at the END of a SOAP body using the JAXWS handlers as so:
HTTP/1.1 200 OK
Content-Type: text/xml;charset=UTF-8
Content-Length: 131
Content-Length: 131
Server: Jetty(7.x.y-SNAPSHOT)
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Body></SOAP-ENV:Body></SOAP-ENV:Envelope>
AA
The problem is that if you try to add them to the SOAP body (see code below) you get a XML Unmarshalling exception. If I add "AA" as a soap attachment I get MORE than 2 caracters after the SOAP body (which I don't want)
Here is the my SOAPHandler code :
@Override
public boolean handleMessage(SOAPMessageContext mc) {
if (Boolean.TRUE.equals(mc.get(MessageContext.MESSAGE_OUTBOUND_PROPERTY))) {
try {
SOAPMessage message = context.getMessage()
String stringSoapMessage= getMsgAsString(message);
stringSoapMessage += "ss";
message.getSOAPPart().setContent((Source) new StreamSource(new ByteArrayInputStream(msg.getBytes())));
message.saveChanges();
context.setMessage(message);
} catch (Exception e1) {
return true;
public String getMsgAsString(SOAPMessage message) throws SOAPException {
String msg = null;
try {
ByteArrayOutputStream baos = new ByteArrayOutputStream();
message.writeTo(baos);
msg = baos.toString();
} catch (Exception e) {
e.printStackTrace();
return msg;
so my question is this: is there any way to add exactly 2 non xml caracters at the end of the soap body using jaxws handlers ? I have spent several weeks on this so it is not an easy question...
Thanks,
Fred.

Yes I have done it using CFX interceptors. But the runtime dependencies needed were too big for this particular use. I mean having to use these:
apache/cxf/cxf-bundle/2.6.0/cxf-bundle-2.6.0.jar
org/apache/neethi/neethi/3.0.2/neethi-3.0.2.jar
wsdl4j/wsdl4j/1.6.2/wsdl4j-1.6.2.jar
/org/codehaus/woodstox/wstx-asl/3.2.4/wstx-asl-3.2.4.jar
org/apache/ws/xmlschema/xmlschema-core/2.0.2/xmlschema-core-2.0.2.jar
org/mortbay/jetty/jetty-util/6.0.2/jetty-util-6.0.2.jar
org/eclipse/jetty/jetty-util/7.5.4.v20111024/jetty-util-7.5.4.v20111024.jar
org/apache/geronimo/specs/geronimo-servlet_2.5_spec/1.1.2/geronimo-servlet_2.5_spec-1.1.2.jar
org/apache/geronimo/specs/geronimo-javamail_1.4_spec/1.7.1/geronimo-javamail_1.4_spec-1.7.1.jar
org/apache/geronimo/specs/geronimo-servlet_3.0_spec/1.0/geronimo-servlet_3.0_spec-1.0.jar
org/eclipse/jetty/jetty-http/7.5.4.v20111024/jetty-http-7.5.4.v20111024.jar
org/eclipse/jetty/jetty-server/7.5.4.v20111024/jetty-server-7.5.4.v20111024.jar
org/eclipse/jetty/jetty-io/7.5.4.v20111024/jetty-io-7.5.4.v20111024.jar
org/eclipse/jetty/jetty-continuation/7.5.4.v20111024/jetty-continuation-7.5.4.v20111024.jar
to add two caracters at the end of a soap message seems like over kill. If this is the only way to do this then i'll do it this way but it just seems like the implementation of the JAXWS API in JDK 6 seems inches away from being able to do this no ?
Thanks for the replies,
Fred

Xml data into non-xml database.. solution anyone?

Hi,
My current project requires me to store the client's data on our servers. We're using Oracle9i. Daily, I will download the client's data for that day and load it into our database. My problem is that the data file is not a flat file so I can't use sql*loader to load the data. Instead, the data file is an xml file. What is the best way to load xml data into a non-xml database? Are there any tools similar to sql*Loader that will load xml data into non-xml database? Is it the best solution for the client to give me an XML dump of their data to load into our database, or should I request a flat file? My last resort would be to write some sort of a script to parse the xml data into a flat file, and then run it through sql*loader. Is this the best solution? One thing to note is that these files could be very large.
Thanks in advance.
-PV

I assume that just putting the XML file into an
extremely large VARCHAR field is not what you want.
Instead, you want to extract data elements from the
XML and write them to columns in a table in your
database. Right?Yes. Your assumption is correct.
It sounds like you already have a script that loads a
flat file into your database. In that case I would
write an XSL transformation that converts the client's
XML into a correctly-formatted flat file.Thank you. I'll look into that. Other suggestions are welcome.

Folders that having non-ascii chars are not displaying on MAC using JFileChooser

On MAC OS X 10.8.2, I have latest Java 1.7.25 installed. When I run my simple java program which allows me to browse the files and folders of my native file system using JFileChooser, It does not show the folders that having non-ascii char in there name. According this link, this bug had been reported for Java 7 update 6. It was fixed in 7 Update 10. But I am getting this issue in Java 1.7.21 and Java 1.7.25.
Sample Code-
{code}
public class Encoding {
public static void main(String[] arg) {
try {
//NOTE : Here at desktop there is a folder DKF}æßj having spacial char in its name. That is not showing in file chooser as well as while is trying to read for FILE type, it is not identify by Dir as well as File - getting File Not Found Exception
UIManager.setLookAndFeel(UIManager.getSystemLookAndFeelClassName());
} catch (IllegalAccessException ex) {
Logger.getLogger(Encoding.class.getName()).log(Level.SEVERE, null, ex);
} catch (UnsupportedLookAndFeelException ex) {
Logger.getLogger(Encoding.class.getName()).log(Level.SEVERE, null, ex);
} catch (ClassNotFoundException ex) {
Logger.getLogger(Encoding.class.getName()).log(Level.SEVERE, null, ex);
} catch (InstantiationException ex) {
Logger.getLogger(Encoding.class.getName()).log(Level.SEVERE, null, ex);
JFileChooser chooser = new JFileChooser(".");
chooser.showOpenDialog(null);
{code}

Hi,
Did you try this link - osx - File.list() retrieves file names with NON-ASCII characters incorrectly on Mac OS X when using Java 7 from Oracle -…
set the LANG environment variable. It's a GUI application that I want to deploy as an Mac OS X application, and doing so, the LSEnvironment setting
<key>LSEnvironment</key> <dict> <key>LANG</key> <string>en_US.UTF-8</string> </dict>

[SOLVED] Non english chars kdemod 4 problem

Hello, I have a little problem with KDE and the non english charactes.
If I open a file with non english chars in its name I get something like this:
(In this case kwrite opens "other" file but in other applications it fails with an error of file not found)
Other sympton is that in KDE menu my name have bad chars too:
(It must be López)
And the third sympton is that if try to rename a file in the desktop, I can't write accented chars (á é í ó ú). At the begining the keyboard in this rename dialog was totally in english but i have got a semi spanish keyboard (i can write ñ letters) with the apropiate /etc/hal/fdi/policy/10-keymap.fdi file.
But the most strange is that in general, in all Kde and non-kde applications and even in the console, non english chars works ok. I can go to the file->Open menu of the application and open a file with non english chars in its name. The problem seems to reside in the part of kde that passes the name of the file to the application (¿kwin?)
my locale is es_ES@UTF8 and as I said I have configured correctly the 10-keymap.fdi file.
I have read in some forums that something like this could be a kde or qt bug, but for me it's not clear as i don't see a general complaining about this.
Any idea will be apreciated.
Thanks in advance,
Christian.
Last edited by christian (2009-03-27 14:52:17)

SanskritFritz wrote:
That should be "es_ES.utf8"
Sorry, i mispelled it in the post.
Of course, my locale is es_ES.utf8:
LANG=es_ES.utf8
LC_CTYPE="es_ES.utf8"
LC_NUMERIC="es_ES.utf8"
LC_TIME="es_ES.utf8"
LC_COLLATE=C
LC_MONETARY="es_ES.utf8"
LC_MESSAGES="es_ES.utf8"
LC_PAPER="es_ES.utf8"
LC_NAME="es_ES.utf8"
LC_ADDRESS="es_ES.utf8"
LC_TELEPHONE="es_ES.utf8"
LC_MEASUREMENT="es_ES.utf8"
LC_IDENTIFICATION="es_ES.utf8"
LC_ALL=
I don't think this could be the source of the problem, because, except in the places I said in the firs post, the rest of my system works perfectly.

How to load file thru reader which contains non-english char in file name

Hi ,
I want to know how to load file in english machine thru reader which contains non-english chars in file names (eg. 置顶.pdf)
as LoadFile gives error while passing unicode converted file name.
Regards,
Arvind

You don't mention what version of Reader? And you are using the AcroPDF.dll, yes?
Sent from my iPad

UploadedFile and filenames with non-ascii chars

Hi
I'm using an UploadedFile object in my web app, and all works fine. However, when I try to upload a file, with a filename containing non-ascii chars (e.g. Spanish), I see that the getBytes method returns an empty byte array, the filename is not stored correctly (the non-ascii chars are lost, replaced by another representation), and that the content-type is application/octet-stream instead of image/png as supposed to be.
If I rename that same file to have only ascii chars - everything is back to normal.
How can I upload files with non-ascii chars in their name?

Hi, back! Spent a few hours experimenting and found
that everything is working great (including the creation
of international non-ASCII foldernames) when I used
utf-8 encoding in the sieve filters rules for the
the match strings and the folder names... at least
so far so good... for your ref and sorry for bothering.

Can I route non-XML files with NW PI 7.0?

Hello,
I have NW 7.0 PI installed. I need to implement very simple scenario:
1. There are two folders Source and Target
2. Any file (non-XML, binary for example) comes to the Source folder
3. File needs to be picked up and routed without any modifications to the Target folder
Questions:
1. Can I implement that with NW? I guess I can
2. How do I do that? Is there any example or some description of implementing such a simple scenario (I have a few samples on how to implement complex scenarios that work with XML files, but I don't need that complexity)
Thanks in advance.

Hi,
Check out the Sravya's blogs for starters, It has lot of links which will help you to learn various pieces of XI.
Aspirant to learn SAP XI...You won the Jackpot if you read this!-Part I
Aspirant to learn SAP XI...You won the Jackpot if you read this!-Part II
Aspirant to learn SAP XI...You won the Jackpot if you read this!-Part III
Thanks,
Pooja

MDM adapter Non-XML Inbound Messaging

Hi all,
I have a scenario where I transport a csv file via PI (NW711_05_REL) to MDM using the File adapter (sender) and MDM adapter 7.1 7.1 (receiver).
The message is sent through to the MDM port fine, and it seems to choose xml as default file type and PI MSG ID as file name.
This results in an xml file with csv content.
As I want to put the file on the port with its original file type (csv) and name, I need to tweak the MDM adapter a bit. For this I have tried to find MDM specific modules, but have been unable to do so.
I have found a u201Cwork aroundu201D by using u201CSet Adapter Specific Message Attributeu201D on the sender file adapter u2013 described on help.sap.com
Configuring the sender file adapter as described in http://help.sap.com/saphelp_nwmdm71/helpdata/en/48/9854884d3217cee10000000a421937/content.htm i am able to set the "FileName" attribute in dynamic configuration.
This enables me to get some of the desired effect, as the file on the MDM port is now a csv file u2013 half way there!! However the file name remains PI MSG ID...
Am I missing something here or is the adapter not working as intended? I donu2019t understand why it should only use the file type when the entire filename and type is there. I would assume that the entire filename and extension would be used in the MDM port.
I have tried achieving the desired result by using the "AF_Modules/DynamicConfigurationBean" on a JMS adapter, but the result is the same.
I would like to avoid developing my own custom module to handle this, as it seems like it should be possible to handle in a more standard way.
I hope someone out there can help me out, and hope to see a lot of good replies.
Best Regards,
Jesper

have you gone thur these settings?
Non-XML Inbound Messaging
When the backend system uses the PI File Adapter sender as the communication channel to deliver messages to the PI server, and the receiving MDM channel corresponds to an inbound MDM port of type other than XML (for example, Flat text file), then you must enable the File Adapter Specific Message Attribute named File Name as follows:
       1.      Edit the corresponding File Adapter sender communication channel.
       2.      In the Advanced tab, choose Set Adapter Specific Message Attribute.
       3.      Choose the File Name.
       4.      Save and activate the changes.
http://help.sap.com/saphelp_nwmdm71/helpdata/en/48/9854884d3217cee10000000a421937/frameset.htm

Flash player will not play flvs from folder with name containing non-Roman Chars

We're trying to play flash as part of a program that can be installed to locations including non-Roman chars (European, Arabic, Chinese, etc.). When the installation path includes any non Roman chars, video will not play. The non-roman chars are garbled when Flash tries to load the flvs. Correct non-Roman chars are: ńśćłł. When loading video it gets translated to: Ĺ„Ĺ›Ä‡Ĺ‚Ĺ‚
We've found this happens whether we are trying to access the video from the xulrunner app or by taking the activities out and running them within an html frame.
Audio on the other hand is no problem
The path information for the xulrunner app from Process monitor is:
Video not found from the video player.
10:41:25.3337898    xulrunner.exe    2316    CreateFile    C:\Pro\Ĺ„Ĺ›Ä‡Ĺ‚Ĺ‚\Flash dll Test\.shared\content\assets\video\VI-d9e37af511faa\Engplus1.flv    PATH NOT FOUND    Desired Access: Generic Read, Disposition: Open, Options: Sequential Access, Synchronous IO Non-Alert, Non-Directory File, Attributes: n/a, ShareMode: Read, AllocationSize: n/a
10:41:25.3339452    xulrunner.exe    2316    CreateFile    C:\Pro\Ĺ„Ĺ›Ä‡Ĺ‚Ĺ‚\Flash dll Test\.shared\content\assets\video\VI-d9e37af511faa\Engplus1.flv    PATH NOT FOUND    Desired Access: Generic Read, Disposition: Open, Options: Sequential Access, Synchronous IO Non-Alert, Non-Directory File, Attributes: n/a, ShareMode: Read, Write, AllocationSize: n/a
Audio found.
10:41:59.7659648    xulrunner.exe    2316    ReadFile    C:\Pro\ńśćłł\Flash dll Test\.shared\content\assets\audio\AU-fa6ed5d31f577\LG0CD1Track06.mp3    SUCCESS    Offset: 0, Length: 4,096, Priority: Normal
10:41:59.7660482    xulrunner.exe    2316    ReadFile    C:\Pro\ńśćłł\Flash dll Test\.shared\content\assets\audio\AU-fa6ed5d31f577\LG0CD1Track06.mp3    SUCCESS    Offset: 4,096, Length: 4,096
Video not found from a flash interactive
10:43:50.0804572    xulrunner.exe    2316    CreateFile    C:\Pro\Ĺ„Ĺ›Ä‡Ĺ‚Ĺ‚\Flash dll Test\.shared\content\assets\flash_interactive\content\FL-123456780l0l\assets\video\video. flv    PATH NOT FOUND    Desired Access: Generic Read, Disposition: Open, Options: Sequential Access, Synchronous IO Non-Alert, Non-Directory File, Attributes: n/a, ShareMode: Read, AllocationSize: n/a
10:43:50.0806413    xulrunner.exe    2316    CreateFile    C:\Pro\Ĺ„Ĺ›Ä‡Ĺ‚Ĺ‚\Flash dll Test\.shared\content\assets\flash_interactive\content\FL-123456780l0l\assets\video\video. flv    PATH NOT FOUND    Desired Access: Generic Read, Disposition: Open, Options: Sequential Access, Synchronous IO Non-Alert, Non-Directory File, Attributes: n/a, ShareMode: Read, Write, AllocationSize: n/a
Audio found from a flash interactive
10:43:50.1928413    xulrunner.exe    2316    ReadFile    C:\Pro\ńśćłł\Flash dll Test\.shared\content\assets\flash_interactive\content\FL-123456780l0l\assets\audio\journa list.mp3    SUCCESS    Offset: 0, Length: 4,096, Priority: Normal
10:43:50.1929148    xulrunner.exe    2316    ReadFile    C:\Pro\ńśćłł\Flash dll Test\.shared\content\assets\flash_interactive\content\FL-123456780l0l\assets\audio\journa list.mp3    SUCCESS    Offset: 0, Length: 25,206, I/O Flags: Non-cached, Paging I/O, Synchronous Paging I/O, Priority: Normal

Not exactly sure what you are doing, but it is obvious that some part of the program you are running does not support multibyte characters like Unicode.
If you are developing that application, make sure it is Unicode enabled. If it is Flash (or Flash Player) that doesn't understand it, then you may not be able to do anything about it.
What I would try if I were to encounter the situation, I would try to use the DOS (8.3) path names, like C:\Documents and Settings would normally be C:\DOCUME~1 or C:\Documents and Settings\All Users would be C:\DOCUME~1\ALLUSE~1 etc.
Use the DIR /X command to find out what the DOS folder names are.

OSB: Retrieve non XML Payload from a service that returns status code 500

Hello,
I'm using OSB 11g.
I have a Business Service that invokes a REST based service (AnyXML). The service I'm calling may return a 500 status code and some JSON-encoded information in the response body containing the remote service error information.
From a Proxy Service, I invoke the Biz Service using a standard Service Call Out. The Call Out works fine if the service doesn't return any error (status code 200).
The problem starts when the service returns a 500 status error: it seems that there is no way to to get hold of the error information (string) that are in the response body. The $fault variable contains some info, but not the actual payload.
I have also tried to "resume" the flow (using a resume action) but no luck.
Is there a way to retrieve a NON-XML payload of a service even if the service returns a 500 status code?
Thanks
Luciano

Hi,
I have same problem, any idea?
I created several Proxy Services between SOA (BPEL) and JDE. Proxy Service works correct, but if interface response has an error (fault) from JDE side, we get high level error message from OSB and we lost error information from endpoints. I want to get following error information from response body, which containing the remote service error information.
e.g. <SOAP-ENV:Fault>:
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Client</faultcode>
<faultstring>[ISS.0088.9134] Exception occurred while processing the body of the message</faultstring>
<faultactor>http://HOST/soap/default</faultactor>
<detail xmlns:webM="http://www.webMethods.com/2001/10/soap/encoding">
<webM:exception> </webM:exception>
</detail>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Until now, I solved errorhandling for Proxy Service with single route node, but if I use Proxy Service for “Failover” and OSB connect to Endpoint 2, BPEL-instances with "fault" state get OSB error message and WSG-Response will be lost from $body of messages.--> error-propagation to client is NOT OK.
Regards,
Moh

Java 5, Linux, 64-bit: Non-ASCII chars over socket

Hi,
I am having issues with reading non-ASCII chars from a socket. I send a mixed message, with the first part in ASCII and the last bit in non-ASCII. There are no issues with reading the non-ASCII characters on Windows. However, when I try running the server on Linux. The following is a message sample:
Start message<CRLF>
фвафывафвыафыв<CRLF>
The second part (which is encoded in either Windows-1250 or KOI8-R), comes out as 3F (when you look at the bytes) on Linux.
Any suggestions?
Thanks,
Max

You must be using Readers and Writers, and you need to make sure you specify the same charsets when constructing them. Don't leave this to the default, as this seems to vary across platforms and definitely has varied across releases.

Non xml char

Similar Messages

Maybe you are looking for