Tom,
Thanks very much for the advice. I will squirrel
it away for future reference. Regarding my original
question about caching in JDBCDescriptorsStore, I have
since stumbled across the answer. Contrary to what I
thought was the cause, it was not a problem with
Oracle's JDBC driver. The code I was using to create
users needed to call NamespaceAccessToken.begin()
before it created the node and
NamespacessAccessToken.commit() immediately
afterwards. When I did that, not only did the
warnings about "No active transaction" go away, the
descriptor store in Oracle was updated immediately. I
wrongly suspected Oracle's JDBC driver because HSql
worked fine as the descriptor store even though I
wasn't calling begin() and commit(). But with Oracle
I found I needed to in order for it to work. Anyway,
I do appreciate your quick and informative responses.
Thanks again,
-kevin
--- Tom Keeney <[EMAIL PROTECTED]> wrote:
> Kevin,
>
> I'm glad I could help in some way. There's one
> caveat though when calling Domain.init() before
> accessing the namespace. I've built a client
> application to add and update Slide /users. Thus I
> needed to call Domain.init() before accessing the
> Namespace. However, there's one drawback. Since I
> initialized the Domain on my own, I don't have
> access to the original Store objects initialized by
> Slide itself. In fact, my client app has created
> its own instances of the Store objects. This means
> I must turn off caching inside of
> AbstractServiceBase so Slide recognizes the updates
> I've made to /users. I understand that the way to
> get around this is to extend WebdavServlet and put
> code there. So just be aware of this caching issue.
>
> Tom
__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
