complexType gives error: could not find type _anon148 in namespace about go-xml HOT 6 CLOSED

This is certainly a bug. Looking at SubDeedType in DeedV2.xsd, I see this:

<xs:complexType name="SubDeedType">
  <xs:sequence>
    <xs:element ref="f:UIC" minOccurs="0" maxOccurs="unbounded">
      ...

and the element being referenced is element UIC in FieldsSchema.xsd

<xs:element name="UIC" >
  <xs:complexType>
    <xs:sequence>
      <xs:element name="CompanyControl" type="xs:string" minOccurs="1" maxOccurs="1"  />
        ...

The xsd package tries to simplify schema by flattening references, like those in SubDeedType, and by naming anonymous types like the one in the UIC element. The documents are much easier to parse & generate code for when there are no references and all types have a name.

You can see this 'simplification' using the aqwari.net/xml/cmd/xsdparse tool. Here's a bit of what it transforms the SubDeedType into:

<xs:complexType name="SubDeedType">
  <xs:complexContent>
    <xs:restriction base="xs:anyType">
      <xs:sequence>
        <xs:element name="UIC" type="_anon148" minOccurs="0" maxOccurs="unbounded" ...

Can you spot the error? _anon148 is not in DeedV2's namespace, it's in FieldsSchema. It should be

        <xs:element name="UIC" type="f:_anon148" minOccurs="0" maxOccurs="unbounded" ...

from go-xml.

After reviewing the code, the bug is in the flattenRef function; when copying a reference to an object in another namespace, it fails to qualify any names contained within.

from go-xml.

I took a look at the flattenRef function, tried to check where this bug could be, but I couldn't find it. Probably, because even after reading the code, logging things, I still don't get completely what's going on.

from go-xml.

I should have time to look at this on the weekend. I believe the error is not handling attributes such as "type", which can contain a QName, here.

from go-xml.

I've added a test that reproduces the issue in a much smaller example, in the import-type-from-otherns branch.

from go-xml.

Thanks for waiting @arjanvaneersel , I ran the command you provided after merging #66 and it produces output now. Please reopen if the issue isn't fixed for you.

from go-xml.