One of our partners (using SeeBeyond eGate) uses different XML prefixes for the same document type. We are extracting custom attributes successfully using one set of prefixes, but get no values when the partner uses the other set of prefixes.
Both prefixes are defined in the namespaces section of the document type.
In IS, I can just populate the nsdecls parameter with one namespace that will work with any XQL query string, but that does not seem to be the case in the TN document type definition.
Should this work? Is there a workaround?