Affects Version/s: None
Fix Version/s: 2.2.1
Security Level: Public (Public: Anyone can view)
KULRICE-8425 Problems with UifBeanFactoryPostProcessor expression handling for nested properties and lists prevent bean property overrides (such as fieldInquiry.render) from working KULRICE-4478 HTML padded with spaces breaking hyperlink KULRICE-9735 Property editor class is initiated Previously with the list<String or any type> but after 2.2.0 upgrade its not happening. KULRICE-3829 KNS RoutingTypeDefinition processing is relying on consistent ordering of two separate lists to hook the right qualificationAttributeName with the right value KULRICE-7563 Easy display of List<String> NEW control(s) KULRICE-9060 add property "additionalCssClasses" to replace "cssClasses" list-merge KULRICE-11279 Default StringListConverter to generate mergeable lists KULRICE-9883 Boolean property value is evaluated as string instead of a boolean KULRICE-9240 UifBooleanEditor Property Editor formatted string values KULRICE-7502 ObjectUtils could not create Object from a collection property with null value
KAI Review Status:Not Required
KTI Review Status:Not Required
String Lists should be rendered as HTML List when bound to an attribute field
Skype Conversation around this:
@Jeremy: You are right I can directly bind a AttributeField to a List<String> but then it renders the value as [value1, value2, value3,....]
Kamal Muthuswamy: We want the values to be rendered stacked one on top of the other
That is why I was thinking maybe binding ti to a CollectionGroup with stacked layoutmanager
Brian Smith: itd be nice to have the ability to output as an actual html list too
Kamal Muthuswamy: at the very least, yes
Kamal Muthuswamy: that way we can controll the style
Kamal Muthuswamy: is that a JIRA?
Jerry Neal: Ok, I see. Let me think. One thing you can do is apply a formatter class (in the recent beta it was changed to property editor). That can be used to build an html list from the property values and then (if editable) populate back from the html
Jerry Neal: So you can create a new class that extends Formatter (CollectionFormatter is an example). Then on your AttributeField specify to use that with the formatterClass property. The Formatter gets called when writing out the value and passes in the value from the object, you use that to build a string which is what will be displayed.
Jerry Neal: Actually CollectionFormatter is probably what is making in come out the way it is now. The formatter you specify will override that
Brian Smith: so maybe jira should be add list formatter?
Jerry Neal: We can create one in the Rice project then when someone needs this they can just specify it. We are using PropertyEditors now though instead of Formatter. Yes that would be great Brian