Details
-
Type:
Task
-
Status: Closed
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: None
-
Component/s: Version Compatibility
-
Labels:None
-
Rice Module:KEW, KIM, KRMS
-
KAI Review Status:Not Required
-
KTI Review Status:Not Required
Description
Figure out how client apps will publish their KimTypeServices via SOAP
1. essentially, we should be able to use this using the support for publishing services with pre-existing wsdl
2. we may want to consider providing custom exporter classes (like KimPermissionTypeServiceExporter) so that they don't have to manually enter the WSDL location
3. Documentation will need to be provided for this
4. for testing we are assuming that we have our standalone client that will handle the callbacks and be built on derby
Attachments
Activity
Bulk update of incomplete 2.0.0-b2 issues to just a 2.0 fix version.
Ok, work here is done now (still need to finish some testing and then commit it though). I put together a quick wiki page here:
https://wiki.kuali.org/x/q1q1Eg
I need to integrate it in with our main body of technical documentation prior to the release. I'll create a separate jira for that.
Ok, CallbackServiceExporter has been committed, existing type services published from standalone rice and the sample app are now using it, and I created the jira to add documentation to the technical guide. Resolving this jira.
Closing since these items are now in the release notes.
Jeremy, you're probably working on this right?