[KULRICE-1841] Make sure reversion of KEW NotificationService implementation is not brought into 0.9.3 if/when rice-release-0-9-3-kfs-080319-br branch is merged into 0.9.3 Created: 14/Apr/08  Updated: 03/Oct/14  Resolved: 22/May/08

Status: Closed
Project: Kuali Rice Development
Component/s: Configuration, Development, Project Management, Quality Assurance
Affects Version/s: None
Fix Version/s: 0.9.3

Type: Task Priority: Major
Reporter: Aaron Hamid (Inactive) Assignee: Eric Westfall
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Rely
relies on KULRICE-1279 Consolidate KEN and KEW notification ... Closed
Rice Team: QA
Rice Module:
KEW, KEN
Application Requirement:
KFS

 Description   

At the end of February, KEW was modified to introduce KCB as a dependency for sending notifications, via the KCBNotificationService implementation defined in KewSpringBeans.xml.

This change was reverted on KFS's branch 'rice-release-0-9-3-kfs-080319-br' so they could move forward in the short term without introducing KCB and KEN.



 Comments   
Comment by Eric Westfall [ 22/May/08 ]

After creating the KFS branch, I modified KewSpringBeans.xml so that it's using the KCBNotificationService.

Generated at Sat Sep 26 10:07:43 CDT 2020 using JIRA 7.0.11#70121-sha1:19d24976997c1d95f06f3e327e087be0b71f28d4.