On Thu, Jan 15, 2009 at 09:03:44PM +0100, Gert Vanthienen wrote:
> From what I gather from our unit tests, this use case is definitely
> supported. One possible guess is that something goes wrong inside Camel
> when converting whatever Source type we get back into a JMS message.
> Could you put a to("log:after-http?showAll=true") right after your HTTP
> call so we can assess the body type? I actually figured out the problem earlier this afternoon - but you're right on the money here: your suggestion would also have shown it up straight away. Our assumption that the XML was being lost was erroneous because we were expecting to see a TextMessage with a String based XML response on the .out queue. Without any conversion to a String.class, we got an ObjectMessage with a DOMSource in it. This is just our unfamiliarity with the tools :( > Is there a difference in behavior when DEBUG logging is turned off in > ServiceMix? The Source type being used is different with DEBUG logging > on and off so it might make a difference here. well funny you should ask, because after I realised what was happening, I changed the camel route to convert to String, verified I got what I'd been looking for all along and then changed logging back to WARN from DEBUG. This now seems to make the route fail! I had to leave at that point but will pick it up again tomorrow. Appreciate you looking at this, thanks. -- Darren Davison Public Key: 0xE855B3EA
signature.asc
Description: Digital signature
