I think I found the problem, I misunderstood the concept of in/out in a processor, I was using the out to add my payload while the quartz object was still in the in body.
But the real problem was with the in header. I had to clear the in header to make this work, somehow the header contained something that jms didn't like. Patrick -----Original Message----- From: davsclaus <[EMAIL PROTECTED]> Sent: Saturday, January 5, 2008 6:21am To: [email protected] Subject: Re: From Quartz to queue Patrick To get faster and better feedback I think you should show us the code and configuration that causes the problem. Maybe creating a small unit test that demonstrates the bug so the Camel team can use this when they find and fix the bug. /Claus Patrick Shea wrote: > > Hi, it seems that anything starting with a quartz endpoint has issues > going to a jms queue. > > I to have a processor to add a string payload to the out message but > somehow the jms message contains some quartz object that get rejected by > the jms queue. > > I have this as an error message: > > Only objectified primitive objects, String, Map and List types are allowed > but was: Trigger 'docs.consumer': triggerClass: 'org.quartz.CronTrigger > isVolatile: false calendar: 'null' misfireInstruction: 0 nextFireTime: Fri > Jan 04 07:17:55 PST 2008 type: class org.quartz.CronTrigger > > Patrrick > > > -- View this message in context: http://www.nabble.com/From-Quartz-to-queue-tp14618552s22882p14633631.html Sent from the Camel - Users mailing list archive at Nabble.com.
