;
>
> JMSConduit conduit = (JMSConduit)client.getConduit();
> conduit.getRuntimePolicy().setMessageType(MessageFormatType.BINARY);
>
>
>
> --
> View this message in context:
> http://www.nabble.com/Nordic-charaters-problem-in-SOAP-MQ-tp15845741p15891076.html
> Sent from the cxf-user mailing list archive at Nabble.com.
>
s message in context:
http://www.nabble.com/Nordic-charaters-problem-in-SOAP-MQ-tp15845741p15891076.html
Sent from the cxf-user mailing list archive at Nabble.com.
at I can see, the
>> å
>> >> looks okay when it is added to W3CDOMXMLStreamWriter.writeCharaters(),
>> >> but
>> >> when the SOAPMessage.writeTo() method is called with System.out or
>> >> OutputStream in SAAJOutInterceptor it is viewed as å.
&
Can you try just using the SAAJ API's in a quick standalone program to
create a soap message then write it out to a file, then read it into a
new SAAJ message and see if the problem remains? If so, it's
definitely a bug in the SAAJ implemenetation. If not, it MAY be an
issue with the JMS t
ded to W3CDOMXMLStreamWriter.writeCharaters(),
> >> but
> >> when the SOAPMessage.writeTo() method is called with System.out or
> >> OutputStream in SAAJOutInterceptor it is viewed as å.
> >>
> >> Can anyone tell me if I can do anything to avoid this behavi
Nino Saturnino Martinez Vazquez Wael wrote:
Nino Saturnino Martinez Vazquez Wael wrote:
mr.andersen wrote:
The idea of escaping the characters is not possible, since the reciever
doesn't expect that.
I guess both sender and reciver should expect it.. Okay no go for
this then...
Just
Nino Saturnino Martinez Vazquez Wael wrote:
mr.andersen wrote:
The idea of escaping the characters is not possible, since the reciever
doesn't expect that.
I guess both sender and reciver should expect it.. Okay no go for this
then...
Just thought of something though, you could try to s
mr.andersen wrote:
The idea of escaping the characters is not possible, since the reciever
doesn't expect that.
I guess both sender and reciver should expect it.. Okay no go for this
then...
The text I'm trying to send throw cxf is hardcoded at this point.
About the encoding for my files
t or
>> OutputStream in SAAJOutInterceptor it is viewed as å.
>>
>> Can anyone tell me if I can do anything to avoid this behaviour or have
>> it
>> something to do with the SAAJ implementation?
>>
>> --
>> View this message in context:
&g
wed as å.
>
> Can anyone tell me if I can do anything to avoid this behaviour or have it
> something to do with the SAAJ implementation?
>
> --
> View this message in context:
> http://www.nabble.com/Nordic-charaters-problem-in-SOAP-MQ-tp15845741p15845741.html
> Sent from the cxf-user mailing list archive at Nabble.com.
>
>
something to do with the SAAJ implementation?
>>
>>
>
> --
> -Wicket for love
> -Jme for fun
>
> Nino Martinez Wael
> Java Specialist @ Jayway DK
> http://www.jayway.dk
> +45 2936 7684
>
>
>
--
View this message in context:
http://www.nabble.com/Nordic-charaters-problem-in-SOAP-MQ-tp15845741p15848433.html
Sent from the cxf-user mailing list archive at Nabble.com.
Hmm, could'nt you just escape it(that would be soft fix)?
this might be a dumb question, but which kind of encoding do you use on
your files? Or are the chars fetched/passed dynamically via db etc?
regards Nino
mr.andersen wrote:
I have at problem with sending nordic charaters such as æøå v
aters-problem-in-SOAP-MQ-tp15845741p15845741.html
Sent from the cxf-user mailing list archive at Nabble.com.
13 matches
Mail list logo
