Hi,
I'm still trying to solve our problem regarding the Cocoon
action that logs accesses to a database table. After more tests and a
few "hacks", we found out that BitstreamReader.java was being "called"
multiple times for one file (we left just one log.info in the setup
method of the BitstreamReader). The problem is that this new action is
called in the map:match for bitstreams, so not only the BitstreamReader
is used multiple times, but the pattern seems like its matched multiple
times too. Large AVI files on Internet Explorer fire at least 3 times
the pattern, but even smaller PDFs seem to have this weird behaviour.
I don't know if it's some sort of bug or some sort of
configuration (our BitstreamReader sets Accept-Ranges to none instead of
not setting it at all, I'm not sure if it's wrong or doesn't matter),
but I think this is not working as it should.
Any ideas?
I know we had a lot of issues that wouldn't exist with 1.5,
and we will soon start working on the upgrade process, but in the
meantime we will have to stay with 1.4.2.
Thanks,
Rafael
------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
