Joined: 13 Mar 2013 Posts: 553 Location: Home Office
NealM wrote:
I would like to point out an additional benefit of using that property; It usually eliminates having to do a lot of CASTs, especially if you are using Mapping Nodes for transforms.
yes, and an important one ( will stop lots of people asking how to CAST to timestamp !! ).
Since v6 is going out of support, maybe the 'Build tree using XML Schema' property can be set on by default in future releases ?
Posted: Sun Aug 11, 2013 7:14 am Post subject: i had this behaviour as well
Newbie
Joined: 11 Aug 2013 Posts: 5
the root cause was that there was an exception later on which made the flow fall back to the input node. I dont remeber exactly, but the way i connected catch and failure terminal caused additional exceptions overwriting the original one and lead to in the end the "dequeue" exception and the message going into the dead letter q.
I solved it by switsching to XMLNSC Parser and no model and connecting a compute node connected to the catch terminal that would analyse the exception and log to some file. That shed some light why things went so bad.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum