> Which Tapestry-IoC version are you using? I tried with both 5.1.0.5 and 5.2.4.
I should also mention that I thought this may have something to do with other advisors (we use them for transaction management as well as checking that a slave database has caught up to a certain point). I've marked all of these to prevent decoration and the specific method where it fails every time is not decorated other than by the timing advice. After more experimentation I can get this to run through with only excluding a handful of methods from the timing advice, all of them in a single service. These methods are always called from methods in other services, so the advice will appear more than once on the call chain. However in many other cases this does not cause any problems. I can't see anything special about any of the methods causing the problems, or the service for that matter, but they do create the problem in a reproducible fashion. A typical signature is public MonthlyStandardReturnsSeries create(TimeSeries timeSeries, MonthRange itv, double[] values); so nothing special. I have methods in the same service that use generic types, e.g. and they cause no problems. Any hint what to look for would be great - seems that this is usually a call out of the javassist generated code, so it is kind-of hard to debug. Cheers, Adriaan --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
