xsd:integer as int / string about gowsdl HOT 8 OPEN

What about using big.Int for xsd:integer?

from gowsdl.

Yeah, that sounds even better than a string, and I'll give it a try when I get back to work in a few days.

from gowsdl.

type XyzTypee big.Int generates "invalid constant type" no matter whether 0 or "0"

from gowsdl.

@danielkwinsor Can you be more specific about what generates that error and what you did?

from gowsdl.

It looks like types_tmpl.go assumes that all restrictions are string enumerations currently.

from gowsdl.

Yeah sure so, originally I changed line 405 of gowsdl.go in the support-for-imports branch -- to "integer": "string",
This worked to compile, though I haven't tested the client yet.

Tried "integer": "big.Int", and hand-imported math/big, but did not change types_tmpl.go
This did not work because

myservice/myservice.go:58: invalid constant type XyzTypee
myservice/myservice.go:60: invalid constant type XyzTypee
myservice/myservice.go:62: invalid constant type XyzTypee
myservice/myservice.go:64: invalid constant type XyzTypee

type XyzTypee big.Int

const (
    XyzTypee0 XyzTypee = "0"

    XyzTypee1 XyzTypee = "1"

    XyzTypee2 XyzTypee = "2"

    XyzTypee3 XyzTypee = "3"
)

from gowsdl.

@danielkwinsor It looks like the problem you're seeing here is that big.Int is not an allowed constant type. Assuming that could be addressed, then the next issue to tackle is that Int.setString will need to be called to parse the enumerated values. Unfortunately, there doesn't seem to be an immutable version of big.Int from my reading of the docs.

from gowsdl.

Now code generates:

type XyzTypee int32

const (
    XyzTypee0 XyzTypee = "0"

    XyzTypee1 XyzTypee = "1"

    XyzTypee2 XyzTypee = "2"

    XyzTypee3 XyzTypee = "3"
)

Expected

type XyzTypee int32

const (
    XyzTypee0 XyzTypee = 0

    XyzTypee1 XyzTypee = 1

    XyzTypee2 XyzTypee = 2

    XyzTypee3 XyzTypee = 3
)

from gowsdl.