Issue Details (XML | Word | Printable)

Key: XFIRE-853
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Tomasz Sztelak
Reporter: Mark Slater
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
XFire

Add the ability to configure in/out/fault handlers with Jsr181HandlerMapping

Created: 22/Jan/07 01:44 PM   Updated: 21/Feb/07 09:35 AM   Resolved: 21/Feb/07 09:35 AM
Component/s: Spring
Affects Version/s: 1.2.4
Fix Version/s: 1.2.5

Time Tracking:
Not Specified

File Attachments: 1. Text File Jsr181HandlerMapping.java.patch (3 kB)



 Description  « Hide

I'm trying to migrate my XFire usage from XFireExporter style of specifying services to the Jsr181HandlerMapping style. One of the things I ran into was that the Jsr181HandlerMapping doesn't support the inHandlers proerty from XFireExporter. I suspect that's because the expected way of doing message handlers with JSR-181 is via the @HandlerChain annotation. Unfortunately, I wasn't able to find a good explanation of how to use this within XFire such that the handlers would be loaded via spring with all their properties wired-in. I did find the @InHandlers annotation that was added to XFire recently, but that had the same problem - the handler object was created without going through Spring, so its dependencies weren't available.

So I came up with my own solution. I simply added the inHandler, outHandler, and faultHandler properties to the Jsr181HandlerMapping class, so they can be wired in just like they were with XFireExporter. And things work beautifully, for me at least.

I've attached a patch file that adds the code to the Jsr181HandlerMapping class.



Tomasz Sztelak added a comment - 21/Feb/07 09:35 AM

Fixed in svn