Code generation issue with enumeration encapsulated in restriction type

[raphaelcotty]

The enumeration class uses encapsulate the enum using the enum name Type.
The class has a getter/setter getType type(0 and setType().
When this enum is encapsulated into a restriction type for example then the generated setter method generates code which tries to check the range generating this code.
Here the restriction length is 2:

rangeOk = rangeOk && (value.value().length() == 2);

The code doesn't compile because value doesn't have a value method.
Maybe adding a value method to the enumeration class returning a string?

[dfaure-kdab]

The first step to get this fixed is to add a unittest, or extend an existing one, with enough WSDL to trigger the issue.

[raphaelcotty]

Pull request added: #235

[dfaure-kdab]

Thanks for the excellent unit test.

Clearly the restriction on length == 2 serves no purpose in this case, the base type already ensures that the string is a value enum value, and all enum values have a length of 2... but I assume you can't change the WSDL file, or that there are use cases where this might be useful (e.g. if some enum values had a different length, as a string...).

I added a stringValue() method and changed the range-check code to use that, in the case of enums ("restrictions").
It actually makes the generated code in the serialize() method cleaner, so I like it :)

[dfaure-kdab]

Fixed in commit 57e02fb

Thanks again for the unittest!