[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: Justification for

[adrian@jboss.org]

"timfox" wrote : That make sense, although I don't see how that applies to the particular methods that have been declared as throws Throwable in messaging core.

Because if everything delcares Throwable, 
you can propogate the Throwable throughout your
internal api without wrapping it at every level.

e.g. for JMS you would wrap the Throwable in a JMSException
in the facade.

You probably aren't aware of the problems we had
due to the stupid jmx exception wrapping. :-)

anonymous wrote : 
  | This is mentioned in Bloch's effective Java "Strive for failure atomicity"
  | 

Not everything can be atomic.
e.g. in the example above, it could be JMS (outside a transaction)
step1 == write the message to a persistent store
step2 == do the processing to add to the queue
a failure in step2 requires
reverseStep1 == remove from the persistent store

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3961346#3961346

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3961346