Hi Florian Pepping, > However, the overall situation concerning performance of animations and > other functions of batik seems to have decreased at the moment. > We tested the (self-builded) trunk version in our application for a few > days, but we have > to step back to the 1.7 version. That's because of many exceptions occur > (concurrent modification, > missing fields and some other) and the animations are somewhat > unaccurate and slow.
It would be great if you could share a few example which would demonstrate the potential regressions, specially regarding performance. I recall a couple of changes which could take up a small additional overhead, but nothing relevant. The concurrent modification issues is definitely worth a better analysis, specially if you are already following the thread-safe recommendations [1] and/or have looked into potential issues within the FAQ [2]. > Perhaps this information may be helpful, otherwise > just leave it anywhere. As state, the information will be increasingly helpful as more details/test cases are provided. Please consider reducing and sharing a few test cases and/or more details: this may, inclusively, help you find bugs and/or architecture problems which may be haunting your own application... ;-) > Thanks and greetings > > Florian Pepping Cheers, Helder Magalhães [1] http://xmlgraphics.apache.org/batik/using/scripting/java.html#N1002A [2] http://xmlgraphics.apache.org/batik/faq.html#N10203 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
