I'm actually not using setRefreshingObjects at all, I'm using
DataContext.performQuery(query, refreshObjects)
Since this is really meaningless now, would it be possible to
deprecate it and replace with DataContext.performQuery(query,
QueryMetaData)?
p.s. the way I do it this way is because the NamedQuery is a singleton
in the EntityResolver. It's easy to forget to set the refresh property
(or cachePolicy as it now is) back.
On 2/12/06, Andrus Adamchik <andru..bjectstyle.org> wrote:
> I just checked - anonymous CVS version seems up to date (e.g.
> QueryMetadata is version 1.3).
>
> But there are some API changes that I mentioned in my message and
> adding to the Wiki as we speak, so you will need to change the way
> you refresh. Instead of "setRefreshingObjects(..)" you should do
> query.setCachePlicy(QueryMetadata.LOCAL_CACHE_REFRESH) or
> query.setCachePlicy(QueryMetadata.SHARED_CACHE_REFRESH), whichever
> applies.
>
> Andrus
>
>
>
>
>
> On Feb 12, 2006, at 4:43 PM, Cris Daniluk wrote:
>
> > This did not work for me. Can you tell me one of the files that
> > changed (I'm not on the CVS list) so that I can verify I got the fix
> > from SF? Sometimes it takes a day for commited stuff to show up.
> >
> > On 2/12/06, Cris Daniluk <cris.danilu..mail.com> wrote:
> >>> No that's ok, it is more important to confirm that it works now (CVS
> >>> or 02/12 nightly build or M11 that I am planning to release later
> >>> today). I added new test cases to test this condition, but if you
> >>> can
> >>> doublecheck that CAY-444 is indeed fixed, it would be awesome.
> >>>
> >>
> >> I'll do a cvs up and test in a few minutes.
> >>
> >> Cris
> >>
> >
>
>
This archive was generated by hypermail 2.0.0 : Sun Feb 12 2006 - 16:59:54 EST