[
https://issues.apache.org/jira/browse/SLING-4665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14516604#comment-14516604
]
Stefan Egli commented on SLING-4665:
------------------------------------
slingIds must be unique throughout the topology. There is no mechanism that
guarantees or establishes this however. While the slingIds are auto-generated
(when they don't exist) - you can't prevent someone from copying an instance
and thus also copy the slingId (although we have explicit documentation stating
that the slingid file must be deleted when doing such a copy).
So for discovery.impl there are checks (SLING-2892, SLING-2901) that at least
detect if in a particular deployment duplicate slingIds can be found.
I'd suggest to do this for all discovery implementations if possible.
So based on this I guess the helper could be slingId based (while doing
paranoia checks at construction time eg)
> Provide a Helper class to compare topology views
> ------------------------------------------------
>
> Key: SLING-4665
> URL: https://issues.apache.org/jira/browse/SLING-4665
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Reporter: Timothee Maret
> Fix For: Discovery Commons 1.0.0
>
>
> As discussed in SLING-4627, the Sling discovery would benefit from having a
> helper class that allow applications to compare two different topology views.
> As suggested by [~egli] this could be developed in a new bundle
> {code}
> <groupId>org.apache.sling</groupId>
> <artifactId>org.apache.sling.discovery.commons</artifactId>
> {code}
> The issue has no component/version assigned as it may require creating a new
> one for discovery.common.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
