Dear Community members,
I am curious if I can create a namespace to save my custom properties. Just like what AEM offers - jcr:title, dc:description, etc . I want to create my own(mysite:customTitle) and use it across my application.
A. is it feasible?
B. If yes, then how to do it? what's the catch and things I must take care of while creating one?
Look forward to your valuable thoughts on this.
Many thanks in advance,
Bilal.
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Yes, it's feasible to add a custom namespace.
1. Open up CRX Explorer by going to http://localhost:4502/crx/explorer/index.jsp. If you are not logged in, select Login and enter Admin credentials for the AEM environment:
2. Select Node Type Administration and in the new window, select Namespaces
3. At the bottom of the window, select New
4. Enter a URL (for now, it doesn’t have to be a real URL, for example, http://weretail.com)
5. Enter a prefix, for example mysite
6. Select OK
Yes, it's feasible to add a custom namespace.
1. Open up CRX Explorer by going to http://localhost:4502/crx/explorer/index.jsp. If you are not logged in, select Login and enter Admin credentials for the AEM environment:
2. Select Node Type Administration and in the new window, select Namespaces
3. At the bottom of the window, select New
4. Enter a URL (for now, it doesn’t have to be a real URL, for example, http://weretail.com)
5. Enter a prefix, for example mysite
6. Select OK
Views
Replies
Total Likes
You create a new custom namespace under, the CRX Explorer, http://localhost:4502/crx/explorer/index.jsp, via @berliant's mention. There are no problems when it comes to registering a new namespace. The catch is you need to set up a namespace for each different AEM environment(s); read is fine.
I am adding one more point to previous answer -
Make sure, your replication user(receiver) should have jcr:namespaceManagement privilege to create namespace on publish.
Views
Replies
Total Likes
It's doable, but I would avoid it. Why? Because you always have to take care that this namespace is registered. Sharing a content package with Adobe support might not be that straight forward anymore.
Full disclosure: I never created custom namespaces in my projects. Worked very well
Views
Replies
Total Likes
Views
Likes
Replies