[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ojb-user
Subject:    Re: ODMG locking and read only references
From:       "Jean-Yves Sironneau" <epsout () gmail ! com>
Date:       2006-03-22 8:50:19
Message-ID: e504ab970603220050s72fe1ca8p () mail ! gmail ! com
[Download RAW message or body]


It worked with the SVN version of OJB the objects are not materialized so
there is no LockNotGrantedException, by weak reference i meant read only
reference to an object, and i that case the referencing object is just
interested by the fact is has a relation with the referenced object but not
with any of it's attributes.

Thanks again for your help.

2006/3/21, Armin Waibel <arminw@apache.org>:
>
> Hi Jean-Yves,
>
> Jean-Yves Sironneau wrote:
> > Hello,
> >
> > I would like to know if it's possible using ODMG to set auto-update to
> > "false" for a reference.
> > Because in the documentation it's supposed to be set to "none". But
> "none"
> > seem's to be "true".
>
> Sorry, the ODMG implementation expects these specific settings and no
> it's not allowed to change these settings.
>
>
> >
> > The issue is that i have a class Role that has a reference on a
> > DocumentBase, when i lock a Role for updating it, it also locks the
> > referenced
> > DocumentBase,
>
> This should only happen if implicit locking is enabled. If you disable
> implicit locking, e.g. at runtime or in OJB.properties file
> http://db.apache.org/ojb/docu/guides/odmg-guide.html
> the referenced objects will not be locked.
> But nevertheless OJB will make a snapshot of the locked object with all
> referenced objects.
>
>
> > and materialize all the proxied objects within DocumentBase to
> > try to write lock them,
>
> OJB should never materialize proxy objects while locking the main
> object. Think there was a bug in <=1.0.4, it's fixed in SVN
> OJB_1_0_RELEASE and will be included in 1.0.5.
> If possible please test latest from SVN OJB_1_0_RELEASE branch.
>
>
> > and i really don't want that has DocumentBase can be
> > big and it's association with Role is just to say that a Role is for
> this
> > DocumentBase, and also because it's throwing a LockNotGrantedExcetion.
> >
>
> Sounds strange. Could it be that the same DocumentBase will be locked by
> different tx?
>
>
> > One solution would be to store the pk of the DocumentBase in Role, but i
> > would like to know if it's possible by keeping a "weak" reference to
> > DocumentBase
> >  or not.
>
> Sorry, I can't see what you mean. How do you currently establish the
> reference? You always need a FK column to define a 1:1 relation. What do
>   "weak" reference mean?
>
> regards,
> Armin
>
>
> >
> > Thank you.
> >
> > Jean-Yves
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-user-help@db.apache.org
>
>


[prev in list] [next in list] [prev in thread] [next in thread]