[
https://issues.apache.org/jira/browse/JCR-3255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13230580#comment-13230580
]
Jukka Zitting commented on JCR-3255:
------------------------------------
The descriptor, not the system property? No objections here.
We normally avoid backporting any non-bugfix changes to maintenance branches to
reduce the chance of unexpected breakage (and to avoid compatibility issues
between two patch releases from the same branch), but the potential impact of a
change like this is so minimal that if you find this feature useful then I'm
fine with backporting it to 2.4 and 2.2.
> Access cluster node id
> ----------------------
>
> Key: JCR-3255
> URL: https://issues.apache.org/jira/browse/JCR-3255
> Project: Jackrabbit Content Repository
> Issue Type: New Feature
> Reporter: Unico Hommes
> Priority: Minor
> Fix For: 2.2.12
>
> Attachments: RepositoryConfigurationParser.patch
>
>
> I need to know the cluster node id in my application. I didn't find any other
> way than to cast to org.apache.jackrabbit.core.RepositoryImpl :
> ((RepositoryImpl)
> session.getRepository()).getConfig().getClusterConfig().getId()
> I would appreciate it if I could get to this using the system property
> ClusterNode.SYSTEM_PROPERTY_NODE_ID.
--
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
