You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Claus Ibsen <ci...@silverbullet.dk> on 2008/06/06 11:19:54 UTC
JAXB MessageType is fucked up - CAMEL-583
Hi
Could the core committers take a peek at CAMEL-583. (Something is rotten in the state of Denmark).
We have a unit tests that has failed all the time but hasn't been picked up since no assertions.
The JAXB stuff for MessageType hasn't been working at all. What are your takes on this?
Med venlig hilsen
Claus Ibsen
......................................
Silverbullet
Skovsgårdsvænget 21
8362 Hørning
Tlf. +45 2962 7576
Web: www.silverbullet.dk
Re: JAXB MessageType is fucked up - CAMEL-583
Posted by James Strachan <ja...@gmail.com>.
Sounds good to me! :)
2008/6/7 Claus Ibsen <ci...@silverbullet.dk>:
> Hi
>
> James I do not think it's worthwhile to move it to a sandbox area that we are not active using. Then the code will just be forgotten there.
>
> What we can do in the short term is to add a few TODO statements that this code does not work because of XXX.
>
> I am sure there are others in the internet world that has the same problem as we do and will find a suitable workaround. We can target a cleanup of this for 1.5/1.6. The public end-users are not using this feature.
>
> I'll add the TODO's in the source.
>
>
> Med venlig hilsen
>
> Claus Ibsen
> ......................................
> Silverbullet
> Skovsgårdsvænget 21
> 8362 Hørning
> Tlf. +45 2962 7576
> Web: www.silverbullet.dk
>
> -----Original Message-----
> From: James Strachan [mailto:james.strachan@gmail.com]
> Sent: 6. juni 2008 19:18
> To: camel-dev@activemq.apache.org
> Subject: Re: JAXB MessageType is fucked up - CAMEL-583
>
> 2008/6/6 Claus Ibsen <ci...@silverbullet.dk>:
>> Hi
>>
>> Could the core committers take a peek at CAMEL-583. (Something is rotten in the state of Denmark).
>> We have a unit tests that has failed all the time but hasn't been picked up since no assertions.
>>
>> The JAXB stuff for MessageType hasn't been working at all. What are your takes on this?
>
> This one is my fault - sorry :)
>
> This stuff was basically work in progress; I wanted a way of being
> able to easily marshall messages to disk - keeping all the
> header/property information around; then let them be replayed again
> later on. So I hacked up some experimental code and never got it
> working.
>
> Maybe we should move this code into a sandbox area?
>
> --
> James
> -------
> http://macstrac.blogspot.com/
>
> Open Source Integration
> http://open.iona.com
>
--
James
-------
http://macstrac.blogspot.com/
Open Source Integration
http://open.iona.com
RE: JAXB MessageType is fucked up - CAMEL-583
Posted by Claus Ibsen <ci...@silverbullet.dk>.
Hi
James I do not think it's worthwhile to move it to a sandbox area that we are not active using. Then the code will just be forgotten there.
What we can do in the short term is to add a few TODO statements that this code does not work because of XXX.
I am sure there are others in the internet world that has the same problem as we do and will find a suitable workaround. We can target a cleanup of this for 1.5/1.6. The public end-users are not using this feature.
I'll add the TODO's in the source.
Med venlig hilsen
Claus Ibsen
......................................
Silverbullet
Skovsgårdsvænget 21
8362 Hørning
Tlf. +45 2962 7576
Web: www.silverbullet.dk
-----Original Message-----
From: James Strachan [mailto:james.strachan@gmail.com]
Sent: 6. juni 2008 19:18
To: camel-dev@activemq.apache.org
Subject: Re: JAXB MessageType is fucked up - CAMEL-583
2008/6/6 Claus Ibsen <ci...@silverbullet.dk>:
> Hi
>
> Could the core committers take a peek at CAMEL-583. (Something is rotten in the state of Denmark).
> We have a unit tests that has failed all the time but hasn't been picked up since no assertions.
>
> The JAXB stuff for MessageType hasn't been working at all. What are your takes on this?
This one is my fault - sorry :)
This stuff was basically work in progress; I wanted a way of being
able to easily marshall messages to disk - keeping all the
header/property information around; then let them be replayed again
later on. So I hacked up some experimental code and never got it
working.
Maybe we should move this code into a sandbox area?
--
James
-------
http://macstrac.blogspot.com/
Open Source Integration
http://open.iona.com
Re: JAXB MessageType is fucked up - CAMEL-583
Posted by James Strachan <ja...@gmail.com>.
2008/6/6 Claus Ibsen <ci...@silverbullet.dk>:
> Hi
>
> Could the core committers take a peek at CAMEL-583. (Something is rotten in the state of Denmark).
> We have a unit tests that has failed all the time but hasn't been picked up since no assertions.
>
> The JAXB stuff for MessageType hasn't been working at all. What are your takes on this?
This one is my fault - sorry :)
This stuff was basically work in progress; I wanted a way of being
able to easily marshall messages to disk - keeping all the
header/property information around; then let them be replayed again
later on. So I hacked up some experimental code and never got it
working.
Maybe we should move this code into a sandbox area?
--
James
-------
http://macstrac.blogspot.com/
Open Source Integration
http://open.iona.com