Hi all, There is one exception. Sometimes these "read-only" methods generate some information (structure, RDs, RD, etc) on the fly and store this info at the store level. At this point in time a transaction is required. For this reason all methods (even the read-only) start a transaction, which is mostly not needed for read-only methods. This should not be a big issue, for the real store transaction is done at the enlist point in time. If the read-only method reads only no enlist is called.
Anyway this behavior is confusing, we should (possibly after the release) try to fix it. Best regards, Juergen -----Original Message----- From: Remy Maucherat [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 17, 2001 07.14 AM To: [EMAIL PROTECTED] Subject: Re: transactions in getmethod > Hi all, > > I was looking for some other problem today, and noticed something rather > strange - GetMethod.java doesn't override > methodNeedsTransactionSupport(), so the default of true is used. So all > those harmless GETs are using transactions. > > Is there any reason for this, or is it just an oversight? It looks like an oversight. All the methods which need to return true explicitely do, but methods which would be ok with a false don't override methodNeedsTransactionSupport(). So I would say WebdavMethod.methodNeedsTransactionSupport() should return false (since it's the default). Remy
