On Wednesday, November 26, 2003, at 08:12 AM, Martin Holz wrote:
However, if you use the interceptor, you will have problems with rollbacks. I think, the interceptors are not informed,if a rollback happened.
Btw. there is still a issue with NodeRevisionContent. You must not call
streamContent or readContent in a interceptors "pre" methods, but only
getContent or getContentBytes. Otherwise the store may get an exhausted stream.
On the other side if you call any of those read methods in a interceptors
"post" method, you may not get any content at all.
I'm completely ignorant of the guts of Slide and what is or is not allowed in an interceptor, but if there are issues getting at the content in an interceptor (first of all, thats a bummer!) then perhaps simply adding the URI to a queue for a background indexer is a better
You have access to the content, but must use getContent or getContentBytes as Martin described. These stream input into arrays for multiple access. This certainly can become a problem when content is BIG. But, what else could one do?
Oliver
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
