[
https://issues.apache.org/jira/browse/SLING-4558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Klimetschek updated SLING-4558:
-----------------------------------------
Description:
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 as to whether that "something" must correspond to a bundle or service
name (not necessary) 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.
was:
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 as 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.
> 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 as to whether that "something" must correspond to a bundle or
> service name (not necessary) 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)
