[SWS-427] AbstractEndpointExceptionResolver.resolveException() does not let subclasses have full access to the MethodEndpoint that raised an exception Created: 07/Sep/08  Updated: 04/May/12  Resolved: 13/Sep/08

Status: Closed
Project: Spring Web Services
Component/s: Core
Affects Version/s: 1.5.2, 1.5.3, 1.5.4
Fix Version/s: 1.5.5

Type: Bug Priority: Major
Reporter: Haikal Saadh Assignee: Arjen Poutsma
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File SWS-427.patch    

 Description   

In resolveException(), the MethodEndpoint gets replaced with it's bean name. As a consequence, subclasses can no longer inspect the MethodEndpoint.

Discussion in this thread: http://forum.springframework.org/showthread.php?p=200392.



 Comments   
Comment by Haikal Saadh [ 18/Sep/08 ]

Thanks, guys, for fixing this. Any ideas if we'll see, say, a milestone build or something?

I need to decide whether to:
a) Wait for 1.5.5
b) Start using a nightly
c) Implement a workaround until 1.5.5 comes out.

Comment by Tareq Abedrabbo [ 18/Sep/08 ]

Well, I reckon you could use the nightly builds while waiting for the final 1.5.5 release.
You can get the snapshots here:
http://static.springframework.org/spring-ws/downloads/1.5-snapshot-download.php

Comment by Arjen Poutsma [ 04/May/12 ]

Closing old issues

Generated at Sun Dec 17 17:40:40 UTC 2017 using JIRA 6.4.14#64029-sha1:ae256fe0fbb912241490ff1cecfb323ea0905ca5.