Hi, > I have the following queries > > a. Is it possible for us to identify with in the content interceptor > the webdav command getting executed.?? > I found that the prestore event (which I was using) getting > triggered when PUT and PROPPATCH commands are executed.
Yes it is : pre/post methods are triggered before/after content to be retrieved, stored (created or updated) or removed. So webdav commands / ContentInterceptor methods call map should be : Copy pre/postStore() Delete pre/postRemove() Get pre/postRetrieve() Head pre/postRetrieve() Mkcol pre/postStore() Move pre/postStore(), pre/postRemove() Options nothing PropFind pre/postRetrieve() PropPatch pre/postStore() Post pre/postStore() Put pre/postStore() Acl, Lock, Unlock ? Could someone complete ;-) If pre/post methods are not called that way, I think it should be fixed. I should add this mapping to documentation. > b. In order to use the Content Interceptor in the multi user > transaction environment we should be able to get a handle > of the transaction/the service object. > c. If the usage of the SERVICEACESSEXCEPTION inside the > event trapping methods is not much used ful as one of the > construction parameter for the exception is the SERVICE. > How do we get the access to the current service object. ??? ContentInterceptors could have been 'ServiceInterceptors' but they are just made to react on content based events, not on service based events. With the help of the above map, ContentInterceptors may be used to react on webdav commands Thanks for raising these questions Regards Jp -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
