Question: Namespaces in DianExtension about ph-ubl

[phax]

The relevant change is 79ea0b6#diff-dfe1409a27a2b239e27cd0306c05e646fbad07757de712619194b107413c52baR43

Additionally I created a quick test to ensure it works: https://github.com/phax/ph-ubl/blob/master/ph-ubl-dian/src/test/java/com/helger/dianubl/DianUBLFuncTest.java#L106

hth

[phax]

Hi Rogger,
from an XML perspective it doesn't matter if the prefix is called "ns2", "dian" or "hugo".
As long as this prefix is mapped to the same URL (e.g. urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2) the XML is considered semantically equal.
But I heard, that DIAN enforces some specific requirements on the namespace prefix if I am not mistaken - I don't know the details. Sorry.

Search through the closed issues for resolutions on how to change the namespaces.

[r-vasquez]

Thanks for the response,

if you see I changed the namespace of cec to ext for this reason using the closed issues examples:

        aNsCtx.addDefaultNamespaceURI("urn:oasis:names:specification:ubl:schema:xsd:Invoice-2");
        aNsCtx.removeMapping("cec");
        aNsCtx.addMapping("ext", "urn:oasis:names:specification:ubl:schema:xsd:CommonExtensionComponents-2");
        aBuilder.setNamespaceContext(aNsCtx);

But since I created a DianExtensionsType instance, marshal it to a DOM Element and then pass the Element to setAny, I cannot control the namespace of this DOM Element from the NamespaceContext from UBL21NamespaceContext instance.

Is there another way to pass the Dian UBLExtension to setAny without having to marshal it to a DOM instance?

[phax]

I get what you mean, and I found no way to marshal the "xs:any" element with the correct namespace URI.

[phax]

I found the problem - the namespace maper was manually overriding the Dian namespace with the default prefix. This will be fixed in 6.6.1