[
https://issues.apache.org/jira/browse/SLING-4558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389843#comment-14389843
]
Alexander Klimetschek commented on SLING-4558:
----------------------------------------------
One could go even further and turn the user.mapping into a jcr property
key/value mapping (using a space instead of ":" as delimiter between the bundle
and service name):
{noformat}
/libs/project/config
+ serviceuser [sling:OsgiConfig]
- "org.example.app.app-bundle myservice" = "myservice-user"
{noformat}
And maybe generalize this ... have an SPI for mapping such special
sling:OsgiConfig nodes based on their node name (if it does not contain a ".").
Then this impl could actually reside in the service user mapping code base.
> Simpler serviceuser config for service user mappings
> ----------------------------------------------------
>
> Key: SLING-4558
> URL: https://issues.apache.org/jira/browse/SLING-4558
> Project: Sling
> Issue Type: Bug
> Components: Installer
> Reporter: Alexander Klimetschek
> Attachments: SLING-4558.patch
>
>
> For a service user configuration (amendment), one has to currently remember a
> weird long PID:
> {{org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended}}
> plus making sure it has a unique ID by appending "-something", which confuses
> people to whether that "something" must correspond to a bundle or service
> name or they come up with these long names:
> {{org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended-org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.amended.something.xml}}
> which then create too long paths for some cases (git checkouts under windows
> or jcr repository limitations).
> A simple "serviceuser" config node name would be better.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
