Hi,
you could try to use the "old" DList implementation instead of the new upcoming one. Change in OJB.properties:
# org.odmg.DList implementation class #DListClass=org.apache.ojb.odmg.collections.DListImpl_2 DListClass=org.apache.ojb.odmg.collections.DListImpl # # org.odmg.DArray implementation class #DArrayClass=org.apache.ojb.odmg.collections.DListImpl_2 DArrayClass=org.apache.ojb.odmg.collections.DListImpl
and see what's going on.
Please can you post exactly what you are doing in your code (source or pseudo code).
regards, Armin
Brian McCallister wrote:
Hmm, is there any chance you can provide a unit test that demonstrates this? Nothing looks immediately wrong with the descriptor.
Do you get the same results if you clear the cache as when you restart the app?
What is the collection type of EquipmentType.specifications?
Did you change your OJB.properties at all between rc4 and rc5?
IIRC there was a change to a couple of the managed collection implementations for ODMG between RC4 and RC5. Armin, were you playing with those?
-Brian
On Dec 23, 2003, at 10:24 AM, Erik Engstrom wrote:
Howdy,
Thanks for the great software! I have just upgraded from RC4 to RC5 and it looks like you guys have made a lot of progress (especially in the docs). I have an issue though, not sure if its something Im doing or if something broke. If I use RC5 my collections are properly stored in the database but are not retrieved when the application is restarted.
Here is a snippet of my repository descriptor:
<class-descriptor class="us.mn.state.dot.freebay.MinimumSpecification" table="MINIMUM_SPECIFICATIONS"> <field-descriptor name="name" column="NAME" jdbc-type="VARCHAR" primarykey="true"/> <field-descriptor name="equipmentTypeId" column="EQTP_TYPE_ID" jdbc-type="INTEGER" required="true" access="anonymous"/> <field-descriptor name="value" column="VALUE" jdbc-type="INTEGER"/> <field-descriptor name="description" column="DESCRIPTION" jdbc-type="VARCHAR"/> <field-descriptor name="units" column="UNITS" jdbc-type="VARCHAR" required="true"/> <field-descriptor name="required" column="REQUIRED_YN" jdbc-type="VARCHAR"
conversion="us.mn.state.dot.freebay.persist.odmg.BooleanToVarcharConver ter"/>
<reference-descriptor name="equipmentType"
class-ref="us.mn.state.dot.freebay.EquipmentType"> <documentation>This is the reference to a MinimumSpecification's EquipmentType</documentation> <foreignkey field-ref="equipmentTypeId"/> </reference-descriptor> </class-descriptor>
<class-descriptor class="us.mn.state.dot.freebay.EquipmentType" table="EQUIPMENT_TYPES">
<field-descriptor name="id" column="TYPE_ID" jdbc-type="INTEGER" primarykey="true" autoincrement="true"/>
<field-descriptor name="name" column="NAME" jdbc-type="VARCHAR"/>
<field-descriptor name="description" column="DESCRIPTION" jdbc-type="VARCHAR"/>
<collection-descriptor name="specifications"
element-class-ref="us.mn.state.dot.freebay.MinimumSpecification" orderby="name" sort="DESC"> <inverse-foreignkey field-ref="equipmentTypeId"/> </collection-descriptor> </class-descriptor>
Under RC4 everything works as expected. Im I doing something wrong here? Im using Postgresql for the database and the ODMG API.
Thanks for your help,
Erik
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
