#1 2012-06-14 18:38:28

fmarin156
Member
Registered: 2010-11-23
Posts: 48

[resolved] problem of encoding with tEsbConsumer

Tags: [encoding, esb, i18n, java]

i have a wsdl with encoding utf8

the external service send a xml with encoding utf8

i set system properties with encoding utf8

and i store the response with tFileOutputXml in utf8

The xml stored contains encoding ISO-8859-15 ...

Where is the mistake ? and how should i manage this ?

thanks for an idea

Fred


Uploaded Images

Offline

#2 2012-06-15 09:45:40

atelesh
Talend team
Registered: 2011-08-09
Posts: 4

Re: [resolved] problem of encoding with tEsbConsumer

check please Advanced settings tab in tFileInputXML and tFileOutputXML components on your job - there is encoding property to configure and by default it set to ISO-8859-15...

Offline

#3 2012-06-15 10:26:27

fmarin156
Member
Registered: 2010-11-23
Posts: 48

Re: [resolved] problem of encoding with tEsbConsumer

Hi, atelesh,

the encoding propriety is set to utf8 (for the tfileoutputxml component)

in fact, i had tfileoutputxml in debugging mode, to see how is the xml send by the external service ...

in the screenshot, you can see the format for the xml send by the external service, and the xml stored by the tfileoutputxml just behind tesbconsumer

perhaps addind a tfileoutputxml is not a good idea, and another component is more transparently ?

regards,

fred

Offline

#4 2012-06-15 14:11:45

eost
Talend Team
Registered: 2010-12-07
Posts: 242

Re: [resolved] problem of encoding with tEsbConsumer

I'm not very good with encodings.  I try to avoid it.  But you might try checking the encoding specified in the XSD referenced of the WSDL.  Does the WSDL use embedded types or does it import an XSD?

Also since you are just dumping the return value from the tESBconsumer, try dumping it with a regular tFileOutput.

Offline

#5 2012-06-15 14:41:12

fmarin156
Member
Registered: 2010-11-23
Posts: 48

Re: [resolved] problem of encoding with tEsbConsumer

Hi, EdwardOst,

there is no XSD in the WSDL, and there are embedded types.

but, when i deploy the wsdl in Studio, it seems that  Talend ESB evaluate a XSD (cf screenchot), and the utf8 encoding is present

as soon as possible, i insert a tfileoutput like you said

greats

fred


Uploaded Images

Offline

#6 2012-06-18 09:51:25

fmarin156
Member
Registered: 2010-11-23
Posts: 48

Re: [resolved] problem of encoding with tEsbConsumer

Hi,

effectively, the dump with a regular tfileoutput is more transparently ... the received xml contains the good encoding tag (encoding UTF8)

thanks

regards,
Fred

Offline

Board footer

Powered by FluxBB