On Sep 29, 2011, at 6:12 PM, sarah_a180 wrote: > When I tag one of my @Singleton beans with a @PostActivate, I am getting the > stack trace below. I can probably work around this for the short term, but a > fix would be nice. :-) > > If you need more information or a sample project, I can probably get that. > (It'd be a little bit of work since our beans are proprietary.)
This is a bug I think is fixed in the coming 4.0.0 beta 1 (uploading those binaries now actually). The issue is that @Singleton beans aren't allowed to have @PrePassivate, @PostActivate methods so the data model we use has (had) read-only lists for those fields. What should be happing and will happen in 4.0.0 is that we will still collect those invalid callbacks and report them more gracefully at the end of deployment with all other issues the app may have. I can't recall offhand if it result in a rejected deployment or us logging that we will ignore those annotations. It will be one of the two. -David
