[SWS-273] AbstractAnnotationMethodEndpointMapping doesn't support proxied bean dependencies Created: 28/Jan/08  Updated: 21/Jul/08  Resolved: 03/Jul/08

Status: Closed
Project: Spring Web Services
Component/s: Core
Affects Version/s: 1.5 M1
Fix Version/s: 1.5.3

Type: Improvement Priority: Major
Reporter: Dan Luputan Assignee: Arjen Poutsma
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

I use PayloadRootAnnotationMethodEndpointMapping with a security interceptor which depends on auto proxied beans.

Since the post processor instance is created, the interceptor dependencies are resolved and so they will not be available for post processing.

The AbstractEndpointMapping is application context aware so it can delay resolving until needed. The simplest solution I see is to be able to set the interceptor names.



 Comments   
Comment by Arjen Poutsma [ 03/Jul/08 ]

This is due to the fact that AbstractAnnotationMethodEndpointMapping (and subclasses, such as PayloadRootAnnotationMethodEndpointMapping), implement BeastPostProcessor. Therefore, a circular state is reached, which results in the procies not working.

I've reimplemented the AAMEM, so that it no longer implements BPP, but works differently. Things should work now.

Comment by Arjen Poutsma [ 21/Jul/08 ]

Closing issues in 1.5.3

Generated at Sat Dec 16 03:28:02 UTC 2017 using JIRA 6.4.14#64029-sha1:ae256fe0fbb912241490ff1cecfb323ea0905ca5.