[KULRICE-11968] make ServiceExporterFactory a Spring-managed bean Created: 21/Feb/14  Updated: 16/Jan/15

Status: Open
Project: Kuali Rice Development
Component/s: Development
Affects Version/s: 2.3.3
Fix Version/s: Backlog
Security Level: Public (Public: Anyone can view)

Type: Improvement Priority: Major
Reporter: Ken Geis Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: Old
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Rice Module:
KSB
KAI Review Status: Not Required
KTI Review Status: Not Required
Code Review Status: Not Required
Include in Release Notes?:
Yes

 Description   

I want to implement an alternate version of SOAPServiceExporter. In order to use it, I need to then use my own ServiceExporterFactory. Unfortunately, this class is a singleton that is concretely referenced by ServiceExportManagerImpl. This means that I need to override three classes in order to change the behavior of just one of them. Rethinking this with inversion-of-control in mind would reduce this to only needing to subclass SOAPServiceExporter and ServiceExporterFactory. Perhaps you could do even better.


Generated at Thu Oct 29 02:52:57 CDT 2020 using JIRA 7.0.11#70121-sha1:19d24976997c1d95f06f3e327e087be0b71f28d4.