It would be better to just deploy the ACS AEM Commons package rather than copying the code. If you have an actual problem using the ACS AEM Commons package, you should report it using GitHub Issues.
The SiteMap servlet gets configured with the resource (component) type, not the template path.Once configured, you can request http://localhost:4502/<path to page>.sitemap.xmlFor example, with weretail, you would configure the servlet with a resource type of weretail/components/structure/page (see s...
This is indeed a limitation -- if both /content/my_company/en_us and /content/my_company/es_es have the same resource type, then they will share the same sitemap servlet instance and thus the same externalizer name.There was some interest about two years ago to make this more flexible, but the issue...
You should be able to do this without any customization in AEM by integrating AEM with ADFS via SAML. I don't know the details of how to configure domain authentication (which I think is what you are describing) in ADFS, but I suspect it is fairly straightforward.FWIW, inside Adobe we do something s...
This is an not the way Sling Models works by default. If there is no @Source annotation (or no custom injector which provides the source value), all injectors are checked. The @Source annotation is just used to refine the scope of annotations checked. You can certainly achieve what you are describin...
As far as I know, there's no existing Transformer which does what you are describing, so you would need to write one.That said, if you are just doing String substitution across the entire HTML document and don't care about the semantic meaning of specific HTML elements, then it is possible that the ...
Ah, I see what you mean now. No, there's no standard approach to do this. If the transformers are all involved are under your control, however, you could accomplish this by sharing some state between the transformers, e.g. set some request attribute in external-tab and then have link-rewrite look at...
I don't think you are using the terminology correctly. For a single request, only a single pipeline will be used, so there are no 'remaining' pipelines.I suspect what you mean to ask if whether a component within a pipeline can remove events so that they are not passed to subsequent components withi...