Hi,

Just a minor request to chain the ResourceException's that are thrown from 
JCAManagedConnectionFactory.

The cause exceptions are being swallowed silently making it rather confusing 
sometimes why things are failing.
As an example, if you have misconfigured the persistence manager the 
ConfigurationException is not chained so you have no idea what the exact 
problem is, as all you get is "unable to instantiate persistence manager" 
instead of "persistence manager has no property 'blah'.

In JCAManagedConnectionFactory, methods openSession and createRepository both 
throw ResourceException without passing the cause exception in the constructor.

 -- Cory

Reply via email to