-
15. Re: Class not found: ReflectionManager
Well, it sounds a very serious issue. JTA transaction support is a big selling point of ModeShape 3.
I agree with you that releasing a product version with such transaction problem is very dangerous.
Our dealine will be end of June, what I expect that ModeShape 3.2 will fix known transaction related issues (mainly around the Hibernate Search/Lucene query).
But as you said it looks like ISPN-604 is another big issue. Although it is targeted to 5.3.0 Final, I'm not sure whether it will cause other issues with ModeShape.
-
16. Re: Class not found: ReflectionManager
Infinispan has been a bit of a pain. I am hoping for 5.3.0.Final for EAP 6.1 as I really want to see ISPN-604 fixed (and it is currently planned for 5.3.0)., I really don't want to release a production version with a transactional problem like that in it. I don't suppose I'm going to get that though am I :-(
No. EAP 6.1.0.Alpha1 was released with Infinispan 5.2.1.Final, and this will be changed to Infinispan 5.2.5.Final sometime before GA. (We're not exactly sure when it will change. Hopefully it will be in the next release, though that might be a Beta.)