On Thu, Dec 18, 2014 at 6:12 PM, Mark Ford <m...@massfords.com> wrote: > I saw that option but it's better suited for JMX. In my case, everything is > resident locally so dumping to XML and having to provide a string adapter > for the payload seems like a lot to do. Also consider that I need to parse > everything back from XML to see what the message is. > > Would you be open to a patch that made made the suspended exchanges easily > accessible through the debugger? For now, I'll add this as a custom > interceptor in my code.
Yeah sure we can do that. We love contributions. The debugger api is really for eclipse / other jvms to remote debug. And hence why its as-is now. > > On Thu, Dec 18, 2014 at 12:00 PM, Claus Ibsen <claus.ib...@gmail.com> wrote: >> >> You can use dumpTracedMessagesAsXml to get the message content in xml. >> >> On Thu, Dec 18, 2014 at 5:26 PM, Mark Ford <m...@massfords.com> wrote: >> > I'm using the BacklogDebugger but don't see an easy way to access the >> > suspended exchanges. The map is private and the SuspendedExchange class >> > itself is also private. While at the breakpoint, I'd like the user to be >> > able to inspect the Exchange. >> > >> > It would help if there were simple getters for this value. I'm not using >> > JMX in this case so I'm not concerned about having to make the Message >> and >> > its content accessible via JMX. >> >> >> >> -- >> Claus Ibsen >> ----------------- >> Red Hat, Inc. >> Email: cib...@redhat.com >> Twitter: davsclaus >> Blog: http://davsclaus.com >> Author of Camel in Action: http://www.manning.com/ibsen >> hawtio: http://hawt.io/ >> fabric8: http://fabric8.io/ >> -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
