You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,6 +23,8 @@ There are several validators included in this artifact, all relate to namespacin
23
23
24
24
Namespacing has been explicitly mentioned in [Achim Koch's Blog: Hosting Multiple Tenants on AEM](https://blog.developer.adobe.com/hosting-multiple-tenants-on-aem-815c8ed0c9f9) but obviously namespacing is just one of multiple aspects to consider for multi-tenant AEM environments.
25
25
26
+
There was also a talk about multi-tenancy and this tool in the [adaptTo 2025 conference](https://adapt.to/2025/schedule/multi-tenancy-and-multi-team-development-in-aem).
27
+
26
28
## Implementation
27
29
28
30
This artifact provides multiple validator implementations for the [FileVault Validation Module][filevault-validation] and can be used for example with the [filevault-package-maven-plugin][filevault-p-m-p] like outlined below.
@@ -124,6 +126,8 @@ You can use this validator with the [FileVault Package Maven Plugin][filevault-p
124
126
</plugin>
125
127
```
126
128
129
+
There is also a project skeleton at <https://github.com/Netcentric/aem-multitenant-demo> which includes these validators with a simple prefix based tenant namespace approach.
130
+
127
131
Adobe, and AEM are either registered trademarks or trademarks of Adobe in the United States and/or other countries.
0 commit comments