[KULRICE-5324] When multiple components have same bean definition in dictionary they get the same id assigned Created: 30/Jun/11  Updated: 13/Oct/11  Resolved: 13/Oct/11

Status: Closed
Project: Kuali Rice Development
Component/s: Development
Affects Version/s: 2.0
Fix Version/s: 2.0.0-m9, 2.0
Security Level: Public (Public: Anyone can view)

Type: Bug Fix Priority: Critical
Reporter: Jerry Neal (Inactive) Assignee: David Elyea
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Similar issues:
KULRICE-7602Dialog Response HTML inputs have same id
KULRICE-12021Kim Attribute problem when multiple attributes have the same name
KULRICE-9218Components for pages not displayed not getting ids causes state issues
KULRICE-10396Extending a bean that has ids on inner beans causes issues, need to define id on inner beans with component id property
KULRICE-8771Collection sometimes creates two components with the same css id
KULRICE-7693expressions in nested bean definitions not processed
KULRICE-12625Attribute definitions not being correctly picked up from data dictionary for input fields
KULRICE-7178When editing a role, the app allows you to add the same user multiple times in the assignee section.
KULRICE-6845Problems with UifBeanFactoryPostProcessor expression handling that is causing bean property overrides (such as fieldInquiry.render) to not work
KULRICE-10373Create group bean definitions for Bootstrap panel and well
Rice Module:
KRAD
KAI Review Status: Not Required
KTI Review Status: Not Required

 Description   

If a component has the same bean definition (same properties) set it will get the same id assigned. This is even if the instance is different because the id is just associated with the bean definition.

We need to prevent this by keeping a map of seen ids and if the component is in there increment.

This is missing up quickfinders and inquiry links.



 Comments   
Comment by Jerry Neal (Inactive) [ 12/Oct/11 ]

I don't believe this is an issue anymore since we redid the logic. The only thing you have to be careful about is doing a <ref bean> to the same bean in multiple places of the view, since that will result in the same id. If they are changed to <bean parent> they will get unique ids.

Generated at Wed Jul 15 07:23:12 CDT 2020 using JIRA 6.1.5#6160-sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.