All namespaces not used in node type definitions missing from the export about aem-nodetypes HOT 14 CLOSED

by what process was the list of namespaces defined? manually or in some automatic process?

This is explained in

I don't know why the crx namespace is not contained in that dump. @stefanseifert Do you have any idea how to get the full dump?

from aem-nodetypes.

I just checked http://localhost:4502/crx/explorer/nodetypes/list.jsp?view=cnf&selection= and also that does not have the crx namespace....

It seems that the CND for some reason always only includes those namespaces which are used in node type definitions, but not those which are just used with property names/node names outside of NT definitions....

That is a shame as CND actually stands for "Compact Namespace and(!) Node Type Definition" (https://jackrabbit.apache.org/jcr/node-type-notation.html)

from aem-nodetypes.

it's there if you look at http://localhost:4502/crx/explorer/ui/namespace_editor.jsp?ck=1606407982435&Path=&Callback=reload

probably the export contains only namespaces defined by CND files, and not those that are added dynamically during the livetime of a repository? (iirc this happens e.g. when uploading assets, they may contain namespaces not known before)

from aem-nodetypes.

The code behind http://localhost:4502/crx/explorer/nodetypes/list.jsp?view=cnf&selection= looks like this

...
 if (req.getParameter("view", "").equalsIgnoreCase("cnf")) {
        response.setContentType("text/plain; charset=utf-8");
        CompactNodeTypeDefWriter cnd = new CompactNodeTypeDefWriter((Writer)out, repSession, true);
        if (ntMgr == null) {
          NodeTypeIterator<NodeType> nodeTypeIterator = repSession.getWorkspace().getNodeTypeManager().getAllNodeTypes();
          while (nodeTypeIterator.hasNext()) {
            NodeType ntImpl = nodeTypeIterator.next();
            if (nodeTypeFilter == 1 && !ntImpl.isMixin())
              continue; 
            if (nodeTypeFilter == 2 && ntImpl.isMixin())
              continue; 
            cnd.write((NodeTypeDefinition)ntImpl);
          } 
        }
...

Probably one would need to call http://jackrabbit.apache.org/api/2.20/org/apache/jackrabbit/commons/cnd/CompactNodeTypeDefWriter.html#write-java.util.Collection-org.apache.jackrabbit.commons.cnd.CompactNodeTypeDefWriter.NamespaceMapping-java.io.Writer- instead internally to also include namespaces not bound to a node type definition. I will investigate, whether there is a servlet exposing that. Otherwise I fear I have to come up with my own implementation for doing a full export.

from aem-nodetypes.

namespaces defined in bundle headers like

Sling-Namespaces: wcmio=http://wcm.io/ns

are also not contained in the output of exportnodetype.jsp.

from aem-nodetypes.

Are those used in nodetypes?
I would rather assume that only namespaces used in nodetypes are exported, the others not. Compare with #2 (comment)

from aem-nodetypes.

no - but the namespace may by used by properties stored in content packages

from aem-nodetypes.

Just to clarify: I do agree that this is a bug and we must export all namespaces, the only question is how to achieve this easily.

from aem-nodetypes.

This version:
aem-2020.11.4506.20201112T235200Z.cnd.txt has been created with a custom servlet now (I will push that later as well).
@stefanseifert WDYT?

from aem-nodetypes.

looks good!
it think this line should be omitted:

<''=''>

from aem-nodetypes.

All future versions will be based on the export from https://issues.apache.org/jira/browse/SLING-9945 which contains all namespaces.

from aem-nodetypes.

thanks!
maybe you should publish an updated version of the AEM 6.5 node type set as well with all namespaces?

from aem-nodetypes.

@stefanseifert Would you be able to provide a PR for 6.5.7?

from aem-nodetypes.

done, created 2 PRs

from aem-nodetypes.