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) <mapping> <class name="com.morixs.mcare.bo.holder.misc.Phone" identity="id"> <description>Eine Telefonnummer</description> <map-to table="PHONE" xml="Phone"/> <field name="id" type="java.lang.Integer"> <sql name="ID"/> <bind-xml name="id" node="element"/> </field> <field name="prefix" type="java.lang.String"> <sql name="PREFIX"/> <bind-xml name="prefix" node="element"/> </field> <field name="number"> <sql name="NUMBER"/> <bind-xml name="number" node="element"/> </field> </class> </<mapping> 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.<init>(FieldMolder.java:791) at org.exolab.castor.persist.ClassMolder.<init>(ClassMolder.java:382) at org.exolab.castor.persist.ClassMolder.resolve(ClassMolder.java:533) at org.exolab.castor.persist.LockEngine.<init>(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