[
https://issues.apache.org/jira/browse/JCR-3255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13226091#comment-13226091
]
Alex Parvulescu commented on JCR-3255:
--------------------------------------
> two JR instances in one JVM
I can see one problem where you start 2 nodes one after the other, the first
one generates an id and sets the system property, then the second one will use
the already set property as the id.
This will break the scenario where you start 2 nodes just to run a simple test
on you local machine, and it can probably affect unit testing / integration
testing as well.
If this is only about convenience, probably adding a method to JctUtils would
be the easiest.
> 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
