n "OJB Users List"
An: OJB Users List <[EMAIL PROTECTED]>
Kopie:
Thema: Re: Antwort: Re: Initializing collection attributes
Hi Gerhard,
> Would you see any obvious problems with this approach? On first glance
it
> seems this could/should be
be done in all caches that keep the references
across transaction boundaries.
Regards,
Gerhard
Armin Waibel <[EMAIL PROTECTED]>
14.10.2003 18:04
Bitte antworten an "OJB Users List"
An: OJB Users List <[EMAIL PROTECTED]>
Kopie:
Thema: Re: Initializ
.
Regards,
Gerhard
Armin Waibel <[EMAIL PROTECTED]>
14.10.2003 18:04
Bitte antworten an "OJB Users List"
An: OJB Users List <[EMAIL PROTECTED]>
Kopie:
Thema: Re: Initializing collection attributes
Hi Gerhard,
this is a known proble
Hi Gerhard,
this is a known problem. Currently caching is not
very sophisticated, but we will start to implement
a really smart two level cache in near future. This
new cache implementation should solve most known problems.
Currently the user have to take care of a consistent
cache.
regards,
Armin
Hi,
I ran into a problem with implementing the collection attribute for a 1:n
mapping:
Since I didn't want to "polute" my persistent objects with any ODMG or
even OJB specific imports, I just initialized my collection attributes (of
type java.util.List) with ArrayLists when needed. This worke
