AW: [castor-user] Strange behavior when reading JDO Mapping
Well, I just had a look at src/main/org/exolab/castor/mapping/mapping.xsd, and it still looks like the type attributes on and 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>
Re: [castor-user] Strange behavior when reading JDO Mapping
Hi Ralf, > what happens if you specify type at the field 'number'? you are right. Your hint solves the problem. Thanks, Andre Teuber
Re: [castor-user] Strange behavior when reading JDO Mapping
Hi List, Ups, this was my fault. Castor 0.9.6 requires exact typ parameters in field section. Castor 0.9.4 has java.lang.String as default value, 0.9.6 has null as default. Nice Problem. Greets Andre Teubner
Re: [castor-user] Strange behavior when reading JDO Mapping
Hi Andre, what happens if you specify type at the field 'number'? Ralf Andre Teubner schrieb: Hello castor list, after upgrading from 0.9.4 to 0.9.6, castor crashs during read the mapping. Our mapping looks like this Mapping (strongly shortened) Eine Telefonnummer Stacktrace: 2005-04-21 13:13:06,893 [main] FATAL A1 - Fehler beim Einlesen der Datenbankkonfiguration || CastorDS.getJDO() L: 156 org.exolab.castor.mapping.MappingException: Unexpected Null pointer! java.lang.NullPointerException at org.exolab.castor.persist.FieldMolder.(FieldMolder.java:791) at org.exolab.castor.persist.ClassMolder.(ClassMolder.java:382) at org.exolab.castor.persist.ClassMolder.resolve(ClassMolder.java:533) at org.exolab.castor.persist.LockEngine.(LockEngine.java:164) java -version java version "1.5.0_01" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_01-b08) Java HotSpot(TM) Client VM (build 1.5.0_01-b08, mixed mode) I figured out, when the field 'number' is comment out (only for test purposes) , everything is fine. So far ok. The realy problem is: We have more than 200 persistent objects in the JDO layer. When i try to load mapping for this other object, castor crash like above. No chance to find out where the next 'field of death' is. Any hints, possible workaround or suggestions? I'm at loss with this problem. Thanks in advance, Andre Teubner -- Syscon Ingenieurbüro für Meß- und Datentechnik GmbH Ralf Joachim Raiffeisenstraße 11 D-72127 Kusterdingen Germany Tel. +49 7071 3690 52 Mobil: +49 173 9630135 Fax+49 7071 3690 98 Email: [EMAIL PROTECTED] Web: www.syscon-world.de
[castor-user] Strange behavior when reading JDO Mapping
Hello castor list, after upgrading from 0.9.4 to 0.9.6, castor crashs during read the mapping. Our mapping looks like this Mapping (strongly shortened) Eine Telefonnummer Stacktrace: 2005-04-21 13:13:06,893 [main] FATAL A1 - Fehler beim Einlesen der Datenbankkonfiguration || CastorDS.getJDO() L: 156 org.exolab.castor.mapping.MappingException: Unexpected Null pointer! java.lang.NullPointerException at org.exolab.castor.persist.FieldMolder.(FieldMolder.java:791) at org.exolab.castor.persist.ClassMolder.(ClassMolder.java:382) at org.exolab.castor.persist.ClassMolder.resolve(ClassMolder.java:533) at org.exolab.castor.persist.LockEngine.(LockEngine.java:164) java -version java version "1.5.0_01" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_01-b08) Java HotSpot(TM) Client VM (build 1.5.0_01-b08, mixed mode) I figured out, when the field 'number' is comment out (only for test purposes) , everything is fine. So far ok. The realy problem is: We have more than 200 persistent objects in the JDO layer. When i try to load mapping for this other object, castor crash like above. No chance to find out where the next 'field of death' is. Any hints, possible workaround or suggestions? I'm at loss with this problem. Thanks in advance, Andre Teubner
