[
https://issues.apache.org/jira/browse/JCR-3255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13226025#comment-13226025
]
Bart van der Schans commented on JCR-3255:
------------------------------------------
The only problem I can think of is when running two JR instances in one JVM. If
that is a concern we could add a method (in the JR api?) to fetch the id. Is
this a real concern or can I go ahead and apply the patch?
> 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
