Well, I just had a look at src/main/org/exolab/castor/mapping/mapping.xsd, and it still looks like the type attributes on <field> and <sql> are considered to be optional. Having said that, it could well be that as part of the numerous modifications to FieldMolder as part of the 0.9. 6 release, we introduced code that does not respect this definition anymore.
If you think that we should still be in-line with this "default behaviour", feel free to raise a bug report at http://jira.codehaus.org. Regards Werner wg> -----Ursprüngliche Nachricht----- wg> Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] wg> Gesendet: Donnerstag, 21. April 2005 14:09 wg> An: user@castor.codehaus.org wg> Betreff: Re: [castor-user] Strange behavior when reading JDO Mapping wg> Wichtigkeit: Niedrig wg> wg> wg> Hi List, wg> wg> Ups, this was my fault. Castor 0.9.6 requires exact typ wg> parameters in wg> field section. Castor 0.9.4 has java.lang.String as default wg> value, 0.9.6 wg> has null as default. Nice Problem. wg> wg> Greets wg> Andre Teubner wg>
