[
https://issues.apache.org/jira/browse/SLING-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12618527#action_12618527
]
Oliver Lietz commented on SLING-592:
------------------------------------
> no, a jcr node name does never reflect a jcr property value.
You are wrong. Go to
http://dev.day.com/microsling/content/blogs/main/opensocialjcr.html and have a
look. There is a picture:
http://dev.day.com/microsling/content/blogs/main/opensocialjcr/docroot/crx.png
You can see a node with name "maija_m" (path:
/content/friends/john_doe/maija_m) and it has three properties. One property is
"name" and its value is the same as the node's name: "maija_m". Node's name
equals node's "name" property.
> please explain what you try to do and what should be added.
example: I want to store lots of shops in the repository and I don't want to
use an artificial node name. I'm happy with
/shops/shop
/shops/shop
/shops/shop
/shops/shop
/shops/shop
/shops/shop
/shops/shop
/shops/shop
I can not use the shops' names because some are equal (but different street,
different city). I don't want to create node names based on shop name, street
and city and I don't want to add an ascending or random number or suffix/prefix
(shop1, shop2, shop2, shop4, ... or name1, name2, othername, ..."client: hey,
why is this shop 1 and the other 2... 2 is bigger so it should be 1.... dev:
.oO(aarrrgghh)").
At the moment you can not load nodes with same name into the repository. So I
would like to see full support for SNS in Sling.
> add SNS (Same Name Siblings) support
> ------------------------------------
>
> Key: SLING-592
> URL: https://issues.apache.org/jira/browse/SLING-592
> Project: Sling
> Issue Type: Improvement
> Reporter: Oliver Lietz
>
> support SNS to simplify adding content without a single unique (meaningful)
> property
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
