[jira] Commented: (JCR-1665) In JCAConnectionRequestInfo, equals() and hashCode() implementations are inconsistent

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

    [ https://issues.apache.org/jira/browse/JCR-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725644#action_12725644 ] 

Jukka Zitting commented on JCR-1665:
------------------------------------

Merged to the 1.x branch in  revision 789706.

> In JCAConnectionRequestInfo, equals() and hashCode() implementations are inconsistent
> -------------------------------------------------------------------------------------
>
>                 Key: JCR-1665
>                 URL: https://issues.apache.org/jira/browse/JCR-1665
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-jca
>    Affects Versions: 1.4
>            Reporter: Roman Puchkovskiy
>            Assignee: Claus Köll
>             Fix For: 1.6.0
>
>         Attachments: JCR-1665.patch
>
>
> JCAConnectionRequestInfo behaves differently in its equals() and hashCode() methods. The former is aware about SimpleCredentials structure, so two instances of JCAConnectionRequestInfo were supplied SimpleCredentials instances with same userID, password and attributes, they are considered equal.
> But JCAConnectionRequestInfo.hashCode() just delegates to SimpleCredentials.hashCode() which is same as Object's method. This breaks session pooling.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.