[jira] Commented: (JCR-1280) Path.equals does not work for other Path implementations

2008-01-15 Thread Julian Reschke (JIRA)

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

Julian Reschke commented on JCR-1280:
-

Of course there are.

One of the reasons for the introduction of the new APIs was to allow 
implementations to use custom Name/Path implementations. In particular, for 
some implementations it will be more efficient to store (prefix, localName), 
others will prefer (namespace, localname).



> Path.equals does not work for other Path implementations
> 
>
> Key: JCR-1280
> URL: https://issues.apache.org/jira/browse/JCR-1280
> Project: Jackrabbit
>  Issue Type: Bug
>  Components: jackrabbit-spi-commons
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>
> PathImpl.equals does not take other path implementations into account (likely 
> a typo).

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



[jira] Commented: (JCR-1280) Path.equals does not work for other Path implementations

2008-01-08 Thread Marcel Reutegger (JIRA)

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

Marcel Reutegger commented on JCR-1280:
---

Is there a use case where two differnt path implementations are tested for 
equality. If not I'd rather suggest to keep the previous check for PathImpl.
Not doing so will likely cause problems when there are implementations that 
extend from PathImpl.

> Path.equals does not work for other Path implementations
> 
>
> Key: JCR-1280
> URL: https://issues.apache.org/jira/browse/JCR-1280
> Project: Jackrabbit
>  Issue Type: Bug
>  Components: jackrabbit-spi-commons
>Reporter: Julian Reschke
>Assignee: Julian Reschke
>
> PathImpl.equals does not take other path implementations into account (likely 
> a typo).

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