xsdgen problem about go-xml HOT 7 CLOSED

Reading through the xsd file, I see FloatType defined as

<xs:complexType name="FloatType">
  <xs:annotation>
    <xs:documentation>
      Representation of floating-point numbers used as measurements.
    </xs:documentation>
  </xs:annotation>
  <xs:simpleContent>
    <xs:extension base="xs:double">
      <xs:attribute name="unit" type="xs:string" use="optional"/>
      <xs:attributeGroup ref="fsx:uncertaintyDouble"/>
    </xs:extension>
  </xs:simpleContent>
</xs:complexType>

So, at least from my initial reading, the problem is that there is no field for the content between the tags. In this case, we should know that the content should be captured by the use of <simpleContent> in the definition of FloatType, so I can add a field to the xsd.SimpleType and xsd.ComplexType types to denote that its content is significant. However, I need to re-read the spec to determine if this covers all cases.

from go-xml.

I'm actually having some trouble coming up with what the desired type declaration would be. Presumably something like

type LatitudeBaseType struct {
	Unit       string  `xml:"unit,attr"`
	PlusError  float64 `xml:"plusError,attr"`
	MinusError float64 `xml:"minusError,attr"`
	Value float64
}

The problem I'm having is getting the right struct tag for the encoding/xml package to unmarshal the content into the Value field. Here's a simplified example: https://play.golang.org/p/05LsLKSHKe

from go-xml.

It looks like this will work:

type LatitudeBaseType struct {
	Unit       string  `xml:"unit,attr"`
	PlusError  float64 `xml:"plusError,attr"`
	MinusError float64 `xml:"minusError,attr"`
	Value float64 `xml:",chardata"`
}

from go-xml.

To answer my previous question, a complex type should capture character data when its content is made of simpleContent or complexContent with mixed=true.

from go-xml.

OK, actually reading the code, it appears that I was already handling a similar case, here, where the chardata field is added if a complex type extended a simple type. However, it did not catch the case where a complex type restricted a complex type that extended a simple type. I'm getting dizzy...

from go-xml.

Hi @junghao , thanks for your patience. PR #10 should have fixed this issue. Here's a snippet of the code generated from your xsd:

// Base latitude type. Because of the limitations of schema, defining
// this type and then extending it to create the real latitude type is the only way to
// restrict values while adding datum as an attribute.
type LatitudeBaseType struct {
	Value      float64 `xml:",chardata"`
	Unit       string  `xml:"unit,attr"`
	PlusError  float64 `xml:"plusError,attr"`
	MinusError float64 `xml:"minusError,attr"`
}

Let me know if that works for you.

from go-xml.

Cool, it's been fixed. Thank you very much.

from go-xml.