Hi Tom,
I don't know if this suggestion is of any
practical use to you, but have you confirmed that your
code is calling NamespaceAccessToken.begin() just
before it tries to update Slide and
NamespaceAccessToken.commit() immediately afterwards?
You responded a while back to a problem I was having
with caching in JDBCDescriptorsStore; specifically
that it wasn't flushing out data to my Oracle
database. What fixed my problem -- and I'm just
wondering if it's related to what you're describing --
is that I started calling begin() and commit(). I
didn't need to turn off caching in
AbstractServiceBase, just wrap my transaction in calls
to begin() and commit(). If I didn't call those
methods, I would see the code work for some DBs (e.g.,
HSql) and not others (Oracle). I'm just wondering if
you're experiencing a similar caching problem.
Best,
-kevin
__________________________________________________
Do You Yahoo!?
Sign up for SBC Yahoo! Dial - First Month Free
http://sbc.yahoo.com
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
