[TUSCANY-2967] For binding.jms, consider a more natural exception handling strategy for non-XML, non-Object wireFormats

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: Java-SCA-1.x
• Component/s: Java SCA JMS Binding Extension
• Assignee: ant elder
• Reporter: Scott Kurz
• Created: 15/Apr/09 13:56
• Updated: 17/Apr/10 21:37

Description

For the wF.jmsBytes, wF.jmsText cases, (when we're not dealing w/ JAX-WS exceptions/faults mapping to XML), it seems odd that we would give you back a TextMessage/BytesMessage for a normal response but an ObjectMessage for an exception (granted this was partly my idea).

Should we instead do something like a toString() and convert an exception to a String we could place in either a BytesMessage or TextMessage? True, I think fidelity would suffer here and the app on the other end might not be able to reconstitute an exception instance matching the one thrown by the SCA service impl before it was turned into a toString by the SCA binding.jms.

But I wonder if this is too unexpected.... if I'm expecting to receive a response TextMessage and get a ClassCastException because I get an ObjectMessage, that might seem really strange.

Maybe this needs more discussion. I also admit I have no idea what other frameworks involving a map between RPC-ish invocations and JMS apps do with exceptions.