Tim wrote : | In this case the exception is thrown from the postgresql driver. Why should the client have to have all the jars in server/lib in their classpath just so they can see exceptions. That sucks IMO | It certainly does. This is not what I had in mind. I was suggesting to wrap the Messaging server-side exception and forward it to client to provide some sort of information about what happened. In this particular case, the client would receive an exception thrown by our persistence manager saying that there are are problems with the database. No need to send a postgres driver exception class over the wire. The messaging exception classes should be in the client-side messaging jar, no additional effort required here. For more details, obviously the server administrator has to consult the logs, where the database exception must be logged. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3960009#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...