Details
-
Type:
Task
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.1.4, 2.2.2
-
Fix Version/s: 2.2.3
-
Component/s: Development
-
Security Level: Public (Public: Anyone can view)
-
Labels:None
-
Similar issues:
KULRICE-9148Disable SessionDocumentService in the KNS KULRICE-10178 Remove SessionDocumentService from KRAD KULRICE-4421SessionDocumentService can be a performance bottleneck KULRICE-8607KNS KualiDocumentFormBase uses the KRAD Session document service instead of the KNS version. KULRICE-6285BusinessObjectService should use DataObjectMetaDataService instead of BusinessObjectMetaDataService KULRICE-8154Location module uses KNS namespace 'KR-NS' KULRICE-12471 Need to add support in code to use the KR-KRAD namespace permissions instead of the KNS namespace permissions KULRICE-5179Convert KNS Formatters to Spring PropertyEditors for use in KRAD KULRICE-8378KNS-based maintenance documents are not using KNS Business Rules classes KULRICE-12292Double check KNS classes still used in KRAD -
Rice Module:KNS
-
KAI Review Status:Not Required
-
KTI Review Status:Not Required
-
Include in Release Notes?:Yes
Description
The KRAD SessionDocumentService is referenced from org.kuali.rice.kns.web.struts.action.KualiDocumentActionBase.loadDocument(), the last line of which is
KRADServiceLocatorWeb.getSessionDocumentService().addDocumentToUserSession(GlobalVariables.getUserSession(), workflowDoc);
Issue Links
- relates to
-
KULRICE-9149
Remove usage of org.kuali.rice.krad.service.impl.SessionDocumentServiceImpl in KRAD
-
Activity
I can not find any other usages in KNS of KRAD's SessionDocumentService.
Committed revision 38069. For KNS (KualiDocumentActionBase) replace usage of KRADServiceLocatorWeb.getSessionDocumentService with KNSServiceLocator.getSessionDocumentService.
Hey Corey, looks like this went into trunk instead of rice-2.2. Hopefully I didn't tell you to do that (which I very well may have), but in any case, a reminder to keep an eye on the fix version 
I merged this down to 2.2.
Hey Corey, while you're at it please double check and make sure that the KRAD SessionDocumentService doesn't get called from anywhere else in the KNS. Thanks!