On Tue, Jun 30, 2009 at 11:28 AM, Simon Laws<[email protected]> wrote: > Hi > > I looked at https://issues.apache.org/jira/browse/TUSCANY-2967 last > week that, after some discussion, ended up at a suggestion for > converting system exceptions to XML in the case that they are thrown > across XML based wire formats. Business exceptions would already be > XML in this case. The advantage being that the sender at least gets > some XML back rather than a serialized Java object which is somewhat > opaque. > > Two question. > > - should we do this?
My 2 cents - unless there's a pressing need I'd not bother and instead push it to the spec group to sort out. We've fiddled with JMS exceptions on just about every Tuscany release since we've had the JMS binding and we've no idea how much thats affecting our users though one did complain once when a new release broke them. If its a non-Tuscany and non-Java client the chances of it being able to handle what ever we return is slim as there are no standard approaches. Having the JMS binding define a separate fault destination would allow for custom wire formats and that seems like to me the most flexible approach suggest so far. All that said though, if anyone really wants to change this to return some XML response that seems fine to me as its sufficiently edge case to likely not affect anyone, i don't think it really matters what the XML looks like, probably as little as possible so its easy to change without breaking clients if/when the spec does get updated to say what to do. ...ant
