Hi The commented sections were at a time when we were trying the solution with Tyrex0.9 version for datasource and J2EEStores. Somehow that tyrex version at that time was complaining about the user playing around with connections and giving us error about the commit and rollbacks. Even with this commented the records were getting commited properly with Tomcat. There should be some archive mails with this regard. This issue is not present in the Tyrex 1.0 and in fact more better implementation wise. So the patch is right. We are still working more on the Slide transaction and J2EEstore to make it more robust. Hoping to submit the finding soon enough.
-- Ashok -----Original Message----- From: Joel Boehland [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 17, 2002 6:56 PM To: [EMAIL PROTECTED] Subject: [PATCH] J2EEStore (schema 2) needs to commit Hi! I have been using the J2EEStore that uses the newer db schema, and I have found a problem when using under jboss/tomcat. For some reason in the commit() and rollback() methods, the sections where the connection is called with connection.commit() or connection.rollback() are commented out, with a comment that says: "Not needed as transactional". I found this to not be true, at least when using the datasource provided with jboss-- nothing will ever be committed to the db. I found that when I uncommented these sections, it all works fine. I am providing a patch that uncomments these sections. I have also included a rough postgresql schema ported from the ones provided for hsql and mssql. It doesn't have any of the referential integrity constraints, as I have found them to cause problems. Hopefully I will have some time to look into this a little more to see if I can add the ref-integrity stuff later. Please let me know if either the patch or the postgresql schema are unacceptable to be included into the slide codebase, and I will try to fix it so that it is acceptable. Thanks! Joel Boehland -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
