Details
-
Type:
Improvement
-
Status:
Open
-
Priority:
Critical
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: 2.6
-
Component/s: Analysis, Development, JPA, KNS Equivalency, Roadmap
-
Security Level: Public (Public: Anyone can view)
-
Labels:
-
Similar issues:
KULRICE-5600Uif Framework: Change Formatter property on AttributeField to PropertyEditor KULRICE-9140Deprecate PersistenceStructureService and related old metadata services KULRICE-11491Remove duplicated test resources from KRAD web framework KULRICE-4258Inconsistent use of Formatters in maintenance framework KULRICE-10120Attribute Definition: Conversion Guide KULRICE-9473 Convert all existing Formatter instances to PropertyEditor KULRICE-9212 Rework KRAD Property Editors/Formatters KULRICE-9889Move deprecated data code and services to the rice-kns module KULRICE-5041Migrate xml import/export framework to the Rice core KULRICE-9556Move all deprecated data/persistence code to rice-kns module -
KRAD Feature Area:Data Dictionary
-
KAI Review Status:Not Required
-
KTI Review Status:Not Required
-
Include in Release Notes?:Yes
Description
I'm not sure exactly what this will mean, but our old-school formatter framework is part of the core.web package at the moment and I think we could do better. I wonder if there are other "formatter" frameworks out there that we should look at (does spring give us something?)
Formatters in core web should be deprecated, new formatters in org.kuali.rice.krad.data.format package. And of course we need to have support in new metadata for this.
Issue Links
- relates to
-
KULRICE-9212 Rework KRAD Property Editors/Formatters
-
1. | Convert all existing Formatter instances to PropertyEditor | KULRICE-9473 | ![]() |
![]() |
Unassigned |
Consider leveraging org.springframework.format?