Gunnar,

I am getting this with 5.0.2.Final and with 5.1.0.Beta1

Is there a way to tell which bean causing the exception?