camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vadim Chekan" <kot.bege...@gmail.com>
Subject Re: xstream marshalling
Date Fri, 19 Sep 2008 16:53:22 GMT
No, they were unrelated. Encoding may affects xml writers behaviour
but not logger.

On Fri, Sep 19, 2008 at 12:09 AM, Claus Ibsen <ci@silverbullet.dk> wrote:
> BTW: Last time there was this "null" message after xstream wans't it also because of
the file.encoding?
>
> Maybe we should write a FAQ entry/or at camel-xstream that if "null" then its lickely
the file.encoding issue.
>
>
>
> Med venlig hilsen
>
> Claus Ibsen
> ......................................
> Silverbullet
> Skovsgårdsvænget 21
> 8362 Hørning
> Tlf. +45 2962 7576
> Web: www.silverbullet.dk
>
> -----Original Message-----
> From: Vadim Chekan [mailto:kot.begemot@gmail.com]
> Sent: 19. september 2008 01:11
> To: camel-user@activemq.apache.org
> Subject: Re: xstream marshalling
>
> Ok, finally I got it.
> In one case javax.xml.stream.XMLOutputFactory was created as
> com.sun.xml.internal.stream.XMLOutputFactoryImpl and in another as
> com.ctc.wstx.stax.WstxOutputFactory.
>
> Ctc implementation worked fine, but Sun's implementation is sensitive
> to file.encoding vm setting and worked on my box only when I set
> UTF-8.
>
> I think it is not a good idea to have a random xml implementation
> being picked up. Should I submit a patch which fixates
> "com.ctc.wstx.stax.WstxOutputFactory"?
> Well, if we expect this implementation, then perhaps static linking
> and creating via old good constructor will be more reliable?
>
> Vadim.
>
> On Thu, Sep 18, 2008 at 2:20 PM, Vadim Chekan <kot.begemot@gmail.com> wrote:
>> This stuff just drives me crazy. I'm hunting it for 3 days.
>> Current release camel is quite unusable with the bug when logger shuts
>> down when message body is null. So I have to switch to current camel
>> snapshot (built by myself).
>>
>> At the moment I know that if I link my test application to the
>> camel-xstream, it works as expected. But when I link directly to
>> camel-xstream.jar then output of marshaler becomes null.
>>
>> Any hints how jar hell problems are troubleshooted?
>>
>> Vadim.
>>
>> On Thu, Sep 18, 2008 at 9:00 AM, Vadim Chekan <vchekan@cox.net> wrote:
>>> No, it is not released yet. I'm just running ahead :)
>>>
>>>
>>> Claus Ibsen wrote:
>>>>
>>>> Hi
>>>>
>>>> No. But since its an upgrade then it could be some classpath issues with
>>>> duplicate .jars on the classpath. Please make sure your classpath is clean
>>>> and correct.
>>>>
>>>> BTW: I haven't seen any announcement on activemq v5.2 being released. Is
>>>> it an official release you are using? Is it in the central maven repo?
>>>> We should have a ticket to upgrade camel as well then.
>>>>
>>>>
>>>> Med venlig hilsen
>>>>  Claus Ibsen
>>>> ......................................
>>>> Silverbullet
>>>> Skovsgårdsvænget 21
>>>> 8362 Hørning
>>>> Tlf. +45 2962 7576
>>>> Web: www.silverbullet.dk
>>>> -----Original Message-----
>>>> From: Vadim Chekan [mailto:kot.begemot@gmail.com] Sent: 18. september 2008
>>>> 00:46
>>>> To: camel-user@activemq.apache.org
>>>> Subject: xstream marshalling
>>>>
>>>> I'm having problem with xstream again.
>>>> I upgraded to activemq-5.2.0 and all the sudden marshaller returns empty
>>>> body.
>>>> And there is no errors at all.
>>>> Does anybody know what could be wrong?
>>>>
>>>>
>>>
>>>
>>
>>
>>
>> --
>> From RFC 2631: In ASN.1, EXPLICIT tagging is implicit unless IMPLICIT
>> is explicitly specified
>>
>
>
>
> --
> From RFC 2631: In ASN.1, EXPLICIT tagging is implicit unless IMPLICIT
> is explicitly specified
>



-- 
>From RFC 2631: In ASN.1, EXPLICIT tagging is implicit unless IMPLICIT
is explicitly specified

Mime
View raw message