Yes something like that is needed but wait a bit before implementing it. I'm still not sure how the J2EE store works. Do you know if the J2EE store is working correctly and why ?
I think something is missing in the store implementation and that's why you also get those wrong content lengths that you reported in your mail "Problem with GET and content Length". A second user sees the new content length before it is committed. In the current implementation, there is only one Connection object and that connection object is used in all threads (for all concurrect requests/transactions). I always had the impression that you had to get a separate connection for each concurrent transaction. Another possebility is that the transaction manager does some magic behind the screens but we are not using a XAConnection, are we? (I don't see the code for this). Ashok, Remy or somebody else can you explain how this J2EE store does its transaction management? Thanks Dirk Colin Britton wrote: > > Actually , I dont think we can merge them back as one since one abstracts > abstractSimpleService and the other abstractService. So at least a helper > classs for the sql methods then. > > We should put the sql (and common code) from both the descriptors and > content versons of the stores in the same helper. > > rgds > CB > ----- Original Message ----- > From: "Colin Britton" <[EMAIL PROTECTED]> > To: "Slide Developers List" <[EMAIL PROTECTED]> > Sent: Saturday, January 12, 2002 2:53 PM > Subject: Re: Database connection lost > > > > We should also think about merging the sql code from JDBC and J2EE > > > stores. > > > > > > > We could merge them back as one store and use a configuration parameter > > (such as if datasource parameter exists) as the key as to which type of > > store it is. If you agree I will get this going. > > > > rgds > > CB -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
