If you return an XML response, then there will be a payload that you can inspect during the onException() clause.
On a side note, you might want to reconsider your approach. We too (my client) are traditionally a .Net shop, but we're using the Java DSL as opposed to the XML DSLs. You'd be surprised how easily folks can transition between the two with the right guidance. I think the Java helps you understand things better, especially when you couple that with test-driven design. It feels more "concrete" that way, IMHO. On Fri, Jun 8, 2012 at 9:05 AM, gramanero <[email protected]> wrote: > Does anyone know if it is possible to interrogate an exception in Camel that > was thrown from a .NET-based endpoint (i.e. a .NET restful service)? I'm > thinking that since the restful service will throw the exception in either > JSON or XML format, that being a string based format (as opposed to binary) > that somehow the underlying .NET exception would be available. All I am > getting from the service is a > org.apache.camel.component.cxf.CxfOperationException exception. I can trap > this in the onException clause, but beyond that I don't know what really > happened. Probably the downside of having to communicate with a .NET service > from a java technology I suppose. > > Oh, and I am hoping to be able to do this in Spring DSL, but would be > interested to know if there is a Java DSL way to do it as well. > > Thanks. > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Question-about-NET-Exceptions-and-the-onException-clause-tp5714201.html > Sent from the Camel - Users mailing list archive at Nabble.com.
