re supported and which not. On the website, it says that the
enumeration facet is supported which seems to be wrong :-(
cheers nick
-Ursprüngliche Nachricht-
Von: Nick Laqua
Gesendet: Dienstag, 13. April 2004 10:32
An: [EMAIL PROTECTED]
Betreff: Re: [castor-dev] sourcegenerator bug
.
*/
public void setPriceUnit(int priceUnit)
{
this._priceUnit = priceUnit;
this._has_priceUnit = true;
} //-- void setPriceUnit(int)
Nick
-Ursprüngliche Nachricht-
Von: Nick Laqua
Gesendet: Dienstag, 13. April 2004 10:01
An: [EMAIL PROTECTED]
Betreff: [ca
Hi,
after upgrading to 0.9.5.3 and regenerating our xml classes, it seems that castor
doesn't generate correct code for type definitions using restrictions for xsd:int. The
xml fragment looks like this:
Hi,
In my XML Schema I have an integer field named messageVersion, with a default-value.
When I generate java code from this schema, I the default value is properly set for
this field. However, the corresponding boolean _hasMessageVersion isn't set, meaning
it's always 'false' unless explicitl
I have an xdr schema used for and generating the java API's using
castor. Problem is, 3 of the elements in my schema references an xsd
enumeration, which in each of the three cases is named the same. However
in each instance the xsd enumeration is defined as having a different,
mutually exclusive
I have attached updates to two files within the SourceGenerator and one
validator which address the following bugs:
1) When an XML Schema type of NMTOKENS is used, the generated code uses a
NameValidator instance configured to validate a single NMTOKEN. By extending
the NameValidator to accep
