-
Bug
-
Resolution: Done
-
Minor
-
2.3.2.Final
When using the resteasy-spring integration with spring's JavaConfig feature for defining beans – resteasy does not use the beans instantiated and initialized by spring. RESTEASY-511 seems to describe this issue well but the final resolution stated there was no test case and did not if the latest patch corrected the problem. I ran into the same issue with the previous release and had a chance to test out the 2.3.2.Final release with the fix – but it did not fully fix the problem. I took some time to create a test case and worked through a solution. I described the solution in a comment on RESTEASY-511 but I did not seem to have the permission to attach the patch file there. I have attached it to this new ticket.
- relates to
-
RESTEASY-746 resteasy-spring is too restrictive when dealing with @Configuration factory beans
-
- Closed
-