Thursday, August 29, 2002, 10:47:13 PM, you wrote: TW> Bita,
TW> I don't have sample code to show you but I'll try to explain better. Take a TW> look at J2EEDescriptorsStore. It maintains a connection map to support TW> concurrent clients. This way the store knows which connection to use when TW> dealing with a specific thread. What I was suggesting is to save the TW> connection reference in the current thread context (you'll need to create TW> the context yourself, maybe using ThreadLocal). Since at the app layer you TW> only have the handle to NamespaceAccessToken, which means you can't get to TW> the connection map since it's hidden by the store impl. But you can get the TW> connection from your current thread context. Am i making sense? There may be a problem with choosing which connection to pick since each store has its own. Also, not all stores use JDBC connections (FileStore for instance). I still think a more general solution could be useful. It's strange no one predicted that Slide may be only a small part of a larger system (although, maybe this kind of design, ie. pluggable transaction manager is not possible with JTA, I don't know). -- Lukasz Kowalczyk -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
