[JCR-1597] JCARepositoryHandle.login(...) methods never throw NoSuchWorkspaceException

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.4
• Fix Version/s: 1.6
• Component/s: jackrabbit-jca
• Assignee: Claus Köll
• Reporter: Roman Puchkovskiy
• Created: 12/May/08 12:35
• Updated: 13/Aug/09 15:03
• Resolved: 27/May/09 07:40

Description

Call sequence:
JCARepositoryHandle.login(Credentials, String) // (here non-existent workspace is specified for login)
JCARepositoryHandle.login(JCAConnectionRequestInfo)
ConnectionManager.allocateConnection(ManagedConnectionFactory, ConnectionRequestInfo)
...
JCAManagedConnection.openSession(JCAConnectionRequestInfo)
Repository.login(Credentials, String) // here NoSuchWorkspaceException is thrown, catched by JCAManagedConnection.openSession(JCAConnectionRequestInfo), set as linkedException to ResourceException, which is thrown
...
Here (in JCARepositoryHandle.login(JCAConnectionRequestInfo)) ResourceException is caught, its cause is retreived, and, if cause is NoSuchWorkspaceException, it's thrown, else another exception is thrown.

Note, that when exception occures on lower level, it's wrapped in ResourceException using setLinkedException(), but on upper level it's unwrapped using getCause(). But cause is not set by anyone, it's null, so NoSuchWorkspaceException is never thrown here.

Suggested fix is to use same mechanism on both ends: either change wrapping mechanism to exception chaining (new ResourceException(msg, cause)), or unwrap using ResourceException.getLinkedException().