|
From: Thomas R. <tho...@tr...> - 2006-11-17 22:51:59
|
Is there an easy way of preventing JPA or other runtime exceptions propagating across a remote call - the remote caller does not have any JPA jars and should not depend on the persistence implementation used on the other side. Since the JPA exception is wrapped in the DataAccessException there is a problem when this class is de-serialized. Any configuration settings or ready to go solutions for this, before we write a custom one? Thomas |