Can we have i18n in the conf folder in the cloud? If not how to have i18n in the cloud . because there is a concept of mutable and immutable objects.
Solved! Go to Solution.
Views
Replies
Total Likes
Hi @yashu99,
We can't have i18n in /conf. We need to keep it under apps.
its a constraint of AEM as cloud that i18n dictionary translation - Does not work at runtime.
Please check for more features and constraints
https://www.linkedin.com/pulse/aem-cloud-service-glance-vivekanand-mishra/
Mutable vs. Immutable Areas of the Repository
/apps and /libs are considered immutable areas of AEM as they cannot be changed (create, update, delete) after AEM starts (i.e. at runtime). Any attempt to change an immutable area at runtime will fail.
Everything else in the repository, /content, /conf, /var, /etc, /oak:index, /system, /tmp, etc. are all mutable areas, meaning they can be changed at runtime.
Hope this helps
Thanks
Hi @yashu99,
We can't have i18n in /conf. We need to keep it under apps.
its a constraint of AEM as cloud that i18n dictionary translation - Does not work at runtime.
Please check for more features and constraints
https://www.linkedin.com/pulse/aem-cloud-service-glance-vivekanand-mishra/
Mutable vs. Immutable Areas of the Repository
/apps and /libs are considered immutable areas of AEM as they cannot be changed (create, update, delete) after AEM starts (i.e. at runtime). Any attempt to change an immutable area at runtime will fail.
Everything else in the repository, /content, /conf, /var, /etc, /oak:index, /system, /tmp, etc. are all mutable areas, meaning they can be changed at runtime.
Hope this helps
Thanks
Views
Replies
Total Likes