You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Julian Reschke (Created) (JIRA)" <ji...@apache.org> on 2011/10/07 15:43:29 UTC
[jira] [Created] (JCR-3102) InternalVersion.getFrozenNode confused
about root version?
InternalVersion.getFrozenNode confused about root version?
----------------------------------------------------------
Key: JCR-3102
URL: https://issues.apache.org/jira/browse/JCR-3102
Project: Jackrabbit Content Repository
Issue Type: Task
Reporter: Julian Reschke
Priority: Minor
It seems the javadoc for InternalVersion.getFrozenNode is confused:
* Returns the frozen node of this version or <code>null</code> if this is
* the root version.
AFAIU, the frozen node of the root version is always present to capture the node type of the versionable node.
Does anybody recall how this got here? (SVN says it has been there forever)
--
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
[jira] [Assigned] (JCR-3102) InternalVersion.getFrozenNode confused
about root version?
Posted by "Julian Reschke (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke reassigned JCR-3102:
-----------------------------------
Assignee: Julian Reschke
> InternalVersion.getFrozenNode confused about root version?
> ----------------------------------------------------------
>
> Key: JCR-3102
> URL: https://issues.apache.org/jira/browse/JCR-3102
> Project: Jackrabbit Content Repository
> Issue Type: Task
> Components: jackrabbit-core
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Minor
>
> It seems the javadoc for InternalVersion.getFrozenNode is confused:
> * Returns the frozen node of this version or <code>null</code> if this is
> * the root version.
> AFAIU, the frozen node of the root version is always present to capture the node type of the versionable node.
> Does anybody recall how this got here? (SVN says it has been there forever)
--
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
[jira] [Updated] (JCR-3102) InternalVersion.getFrozenNode confused
about root version?
Posted by "Jukka Zitting (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jukka Zitting updated JCR-3102:
-------------------------------
Issue Type: Improvement (was: Task)
> InternalVersion.getFrozenNode confused about root version?
> ----------------------------------------------------------
>
> Key: JCR-3102
> URL: https://issues.apache.org/jira/browse/JCR-3102
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Minor
> Fix For: 2.3.1
>
>
> It seems the javadoc for InternalVersion.getFrozenNode is confused:
> * Returns the frozen node of this version or <code>null</code> if this is
> * the root version.
> AFAIU, the frozen node of the root version is always present to capture the node type of the versionable node.
> Does anybody recall how this got here? (SVN says it has been there forever)
--
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
[jira] [Resolved] (JCR-3102) InternalVersion.getFrozenNode confused
about root version?
Posted by "Julian Reschke (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke resolved JCR-3102.
---------------------------------
Resolution: Fixed
with r1180054
> InternalVersion.getFrozenNode confused about root version?
> ----------------------------------------------------------
>
> Key: JCR-3102
> URL: https://issues.apache.org/jira/browse/JCR-3102
> Project: Jackrabbit Content Repository
> Issue Type: Task
> Components: jackrabbit-core
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Minor
> Fix For: 2.3.1
>
>
> It seems the javadoc for InternalVersion.getFrozenNode is confused:
> * Returns the frozen node of this version or <code>null</code> if this is
> * the root version.
> AFAIU, the frozen node of the root version is always present to capture the node type of the versionable node.
> Does anybody recall how this got here? (SVN says it has been there forever)
--
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
[jira] [Updated] (JCR-3102) InternalVersion.getFrozenNode confused
about root version?
Posted by "Julian Reschke (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke updated JCR-3102:
--------------------------------
Component/s: jackrabbit-core
> InternalVersion.getFrozenNode confused about root version?
> ----------------------------------------------------------
>
> Key: JCR-3102
> URL: https://issues.apache.org/jira/browse/JCR-3102
> Project: Jackrabbit Content Repository
> Issue Type: Task
> Components: jackrabbit-core
> Reporter: Julian Reschke
> Priority: Minor
>
> It seems the javadoc for InternalVersion.getFrozenNode is confused:
> * Returns the frozen node of this version or <code>null</code> if this is
> * the root version.
> AFAIU, the frozen node of the root version is always present to capture the node type of the versionable node.
> Does anybody recall how this got here? (SVN says it has been there forever)
--
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
[jira] [Updated] (JCR-3102) InternalVersion.getFrozenNode confused
about root version?
Posted by "Julian Reschke (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke updated JCR-3102:
--------------------------------
Fix Version/s: 2.3.1
> InternalVersion.getFrozenNode confused about root version?
> ----------------------------------------------------------
>
> Key: JCR-3102
> URL: https://issues.apache.org/jira/browse/JCR-3102
> Project: Jackrabbit Content Repository
> Issue Type: Task
> Components: jackrabbit-core
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Minor
> Fix For: 2.3.1
>
>
> It seems the javadoc for InternalVersion.getFrozenNode is confused:
> * Returns the frozen node of this version or <code>null</code> if this is
> * the root version.
> AFAIU, the frozen node of the root version is always present to capture the node type of the versionable node.
> Does anybody recall how this got here? (SVN says it has been there forever)
--
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
[jira] [Commented] (JCR-3102) InternalVersion.getFrozenNode
confused about root version?
Posted by "Jukka Zitting (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122812#comment-13122812 ]
Jukka Zitting commented on JCR-3102:
------------------------------------
It looks like the null reference in javadoc was added in revision 122838 based on code from revision 53784 [2]. So this dates back to time before JCR 1.0. I guess the javadoc is simply outdated and refers back to the initial idea of the root version not having any frozen state. AFAICT the idea of including basic details of the node in the root version came a bit later.
[1] http://svn.apache.org/viewvc?view=revision&revision=122838
[2] http://svn.apache.org/viewvc?view=revision&revision=53784
> InternalVersion.getFrozenNode confused about root version?
> ----------------------------------------------------------
>
> Key: JCR-3102
> URL: https://issues.apache.org/jira/browse/JCR-3102
> Project: Jackrabbit Content Repository
> Issue Type: Task
> Components: jackrabbit-core
> Reporter: Julian Reschke
> Priority: Minor
>
> It seems the javadoc for InternalVersion.getFrozenNode is confused:
> * Returns the frozen node of this version or <code>null</code> if this is
> * the root version.
> AFAIU, the frozen node of the root version is always present to capture the node type of the versionable node.
> Does anybody recall how this got here? (SVN says it has been there forever)
--
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