[
https://issues.apache.org/jira/browse/SLING-4558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14391319#comment-14391319
]
Alexander Klimetschek commented on SLING-4558:
----------------------------------------------
I know, this patch is mostly intended to trigger some discussion and creativity
in looking for a simpler solution.
Maybe the core problem is that the PIDs are usually long and implementation
class names (since that's the default), and we should rather use simpler names.
In this case the service user mapping could have used something like
"serviceuser" right away. Of course, this requires to think of potential
conflicts and namespacing... And it doesn't solve the "I have to come up with
an -alias" issue.
> 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.
> For reference, the target service is
> [MappingConfigAmendment|https://github.com/apache/sling/blob/trunk/bundles/extensions/serviceusermapper/src/main/java/org/apache/sling/serviceusermapping/impl/MappingConfigAmendment.java]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
