I think I am understanding a bit better what is happening, but not sure if it
should be or how I can prevent it.
I have the following parent object (in brief) to the region object that is
getting removed from cache:
<field-descriptor
name="countryId"
column="countryid"
jdbc-type="CHAR"
/>
<field-descriptor
name="regionId"
column="regionid"
jdbc-type="CHAR"
/>
<field-descriptor
name="localId"
column="localid"
jdbc-type="CHAR"
/>
<reference-descriptor
name="country"
class-ref="comp.places.CountryVO"
auto-retrieve="true"
auto-update="none"
auto-delete="none"
proxy="false">
<foreignkey field-ref="countryId"/>
</reference-descriptor>
<reference-descriptor
name="region"
class-ref="comp.places.RegionVO"
auto-retrieve="true"
auto-update="none"
auto-delete="none"
proxy="false">
<foreignkey field-ref="countryId"/>
<foreignkey field-ref="regionId"/>
</reference-descriptor>
With the objects materialized with a countryId, regionId, and localId all with
values, when the parent object gets updated with the regionId nulled out the
former region seems to be being taken out of cache even though I asked for it
not to be as shown in the first email and the delete attribute is set to
"none". The regions are not getting deleted from the database so when I
restart the server the lists are ok again.
How do I prevent the countries, regions, etc from not being able to be removed
from cache to stop this problem from happening?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
