[KULRICE-4451] Re-examine how RiceApplicationConfigurationService is being used to resolve doc handler urls (and other variables) from across the service bus Created: 18/Aug/10  Updated: 23/Feb/12  Resolved: 25/Oct/11

Status: Closed
Project: Kuali Rice Development
Component/s: Development, Version Compatibility
Affects Version/s: None
Fix Version/s: 2.0.0-b1, 2.0

Type: Improvement Priority: Critical
Reporter: Eric Westfall Assignee: Eric Westfall
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: 1 week
Time Spent: Not Specified
Original Estimate: 1 week

Issue Links:
duplicates KULRICE-5762 Convert riceApplicationConfigurationS... Closed
Similar issues:
KULRICE-2719Create the RiceApplicationConfigurationService for use by rice client applications
KULRICE-5797Fix doc handler url in the AgendaEditor's doctype
KULRICE-10085doc handler url not shown by default email stylesheet
KULRICE-10000Re-examine design and architecture of Kuali ModuleService in terms of cleaning things up for KRAD
KULRICE-12308Add application doc ID to doc handler URL
KULRICE-2581doc handler urls no longer being inherited
KULRICE-985Service Bus does not honor message.persistence property in certain situations
KULRICE-3721The "remote" run mode for KIM (and other Rice modules?) does not allow proper consumption of services from the bus
KULRICE-3428Review all services published from each module and determine which should be exported to the bus under which run modes (local, embedded, remote)
KULRICE-2872Change the KEW DocumentType implementation from being an absolute URL to a relative URL using the config param 'externalizable.help.url'
Rice Module:
KAI Review Status: Not Required
KTI Review Status: Not Required


Currently, if KEW encounters a doc handler url of the following form:




If the document type for that document has a service namespace along the lines of something like "KFS" then it will go to the KFS application first and try and resolve application.url from the KFS application across the service bus.

This is a good idea in theory, however for applications that have doc handler urls that don't need to call back into the application, this extra step adds extra overhead since those variables will never be resolved successfully from the client. It may also be possible in certain cases that you don't want it to resolve from the client. At the very least we need to add some caching in here to reduce the number of times we hit the service bus. Additionally, it may be worthwhile to have the RiceApplicationService have a way to provide the standalone server with information on whether or not those kinds of callbacks into the client application should be used.

Comment by Eric Westfall [ 28/Apr/11 ]

Jeremy, just wanted to put this on your radar as per our discussion this week on this service.

Comment by Jeremy Hanson [ 19/Oct/11 ]

Eric, assigning this to you because you mentioned you might get rid of the RiceApplicationConfigurationService. If that falls through, feel free to assign back to me.

Comment by Eric Westfall [ 25/Oct/11 ]

Work on this issue has been completed as part of KULRICE-5762

Comment by Jessica Coltrin (Inactive) [ 23/Feb/12 ]

Closing since these items are now in the release notes.

Generated at Sat Jul 04 22:46:47 CDT 2020 using JIRA 6.1.5#6160-sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.