Details
-
Type:
Task
-
Status:
Closed
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: None
-
Component/s: Development
-
Security Level: Public (Public: Anyone can view)
-
Labels:None
-
Similar issues:
KULRICE-6491 Add validation to TermSpecification maint doc based on existing TermResolvers KULRICE-832RuleXmlParser inefficiently fetches all rules KULRICE-5723Make sure that we validate that everything within an agenda is valid within that agenda's context KULRICE-6662Apply sql for permission to the Term,TermSpecification and Context to master DB KULRICE-11373Module configurer changes required to have both the module spring MVC and the module services in the same context KULRICE-7626Expose relationship between Context and TermSpecification at the DTO level KULRICE-918Need a way to add context to value finder classes KULRICE-886ServiceLookup Context Object to fetch services through service locators and Return a LocatorResult instead of object from both getObject and getService from locators KULRICE-3882JPA: discover JPA cascade/fetch option mappings vs OJB(auto-xxxx/proxy), find out what conversion scripts have done and will do for it KULRICE-13872When saving a new agenda, user must tab off of context field or use context lookup to prevent validation error -
Rice Module:KRMS
-
KAI Review Status:Not Required
-
KTI Review Status:Pending Review
-
Include in Release Notes?:Yes
Description
It would be really useful for KC to have a new method in KrmsTermRepositoryService to fetch all TermSpecifications for a context. It will provide more flexibility for us to know the TermSpecificationDefinitions before hand and can build the facts using those term keys. One of the user requirement in KC is to create Terms by using Document properties. We can easily achieve this by using reflection if know the Terms while building the facts.
I have done this work locally and tested in both Bundled and Embedded mode.
Peter,
Could you take a look at the patch and see if its appropriate to commit the fix form our side. If you have any other suggestions to get the TermSpecifications for context in any other ways, please suggest that too.
Issue Links
- is related to
-
KULRICE-9857
The changeset for KULRICE-9019 isn't in rice-trunk
-
Activity
Yes Gayathri. Its the final one. Please patch it.
I clarified with Eric and any changes to a published service API need to be run by the KTI. This one is small enough that we can probably just send a message to the list informing them of the change.
Hi Peter,
Thanks for the comments. I fixed those and attached the patch. Could you review it again and see if its good to go.
Geo
attached the new patch to the review.
Ok, I emailed the KTI list to notify them about this change. That thread can (hopefully) be found here: https://groups.google.com/a/kuali.org/forum/?hl=en&fromgroups=#!topic/rice.kti/S0NVMp1pd8c
Gayathri,
This is working as desired. Please resolve this.
Geo, the Rice 2.1.4 RC is coming out next week, we need to get this reviewed and committed asap if you want it. Is this patch final or are there additions?