[jira] [Updated] (JCR-2798) JCAManagedConnectionFactory should chain cause exception

["Jukka Zitting (Updated) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/JCR-2798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting updated JCR-2798:
-------------------------------

    Fix Version/s:     (was: 2.4)
                   2.3.3
    
> JCAManagedConnectionFactory should chain cause exception
> --------------------------------------------------------
>
>                 Key: JCR-2798
>                 URL: https://issues.apache.org/jira/browse/JCR-2798
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-jca
>    Affects Versions: 2.1.1
>            Reporter: Cory Prowse
>            Assignee: Claus Köll
>            Priority: Minor
>             Fix For: 2.3.3
>
>
> In JCAManagedConnectionFactory, methods openSession and createRepository both throw ResourceException without setting the cause exception.  This can result in the actual error being swallowed silently, and only stepping through the running code at this point will reveal the actual error (eg: Persistent Store configuration error will appear as a pool exception).
> Jukka Zitting on 12-Oct-2010 said:
> This constructor is not available in J2EE version 1.3, so for now
> we've been using the ResourceException.setLinkedException() method for
> this (see JCR-761). To address your need we could either upgrade the
> platform requirement to J2EE 1.4 or start using the J2SE method
> Exception.initCause() instead of setLinkedException(). Can you file an
> improvement issue in Jira about this?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira