Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of willem.jiang@gmail.com
 designates 209.85.160.45 as permitted sender)
Date: Fri, 19 Oct 2012 15:26:47 +0800
From: Willem jiang <willem.jiang@gmail.com>
To: users@camel.apache.org
Message-ID: <5354F88259B44E7B8416C1F363739A53@gmail.com>
In-Reply-To: <1350554730254-5721226.post@n5.nabble.com>
References: <1350484821476-5721182.post@n5.nabble.com>
 <A761088211A64839A028A328F2ED4F70@gmail.com>
 <1350542062916-5721218.post@n5.nabble.com>
 <460D6683E4EA45D7913C167A1084B1EE@gmail.com>
 <1350554730254-5721226.post@n5.nabble.com>
Subject: Re: Strange problem when bridging amq to cxf
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Yeah, camel-jms component need the message body to be Serializable.
Or you need to marshal and unmarshal the POJO with JAXB or other date format.

BTW, I just committed the test into the trunk[1]

[1]http://svn.apache.org/viewvc?rev=1399986&view=rev 

-- 
Willem Jiang

Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English)
          http://jnn.javaeye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang 
Weibo: willemjiang


On Thursday, October 18, 2012 at 6:05 PM, jkob wrote:

> Finally I found out what is the problem.
> 
> Some web services return POJOs that are serializable but don't implement the
> Serializable interface. It seems camel is not able to do the unmarshalling
> then.
> 
> 
> 
> --
> View this message in context: http://camel.465427.n5.nabble.com/Strange-problem-when-bridging-amq-to-cxf-tp5721182p5721226.html
> Sent from the Camel - Users mailing list archive at Nabble.com (http://Nabble.com).