|Summary:||Role labels need to come from the DB|
|Product:||Red Hat Network||Reporter:||Ryan Bloom <rbb>|
|Component:||RHN/R&D||Assignee:||Mike McCune <mmccune>|
|Status:||CLOSED NOTABUG||QA Contact:||Fanny Augustin <fmoquete>|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2004-10-28 20:31:10 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Bug Depends On:|
Description Ryan Bloom 2004-08-04 16:18:20 UTC
Currently, the role labels are static strings in the DB and in the Role class. This means that whenever we modify the list of possible roles, we have to update 2 locations to reflect that change. The DB is the authoritative list of roles, the Roles class should load the possible roles from the DB. For an example, OrgFactory gets the list of entitlement labels from the DB.
Comment 1 Ryan Bloom 2004-10-28 20:31:10 UTC
This isn't a bug. We need to have some way to reference the Roles that are stored in the DB. Either that is with static strings used to do a lookup, or with static objects retreived from the DB. Either way, when you add a role to the DB, you will need to also add a line of code to add that concept to the Java code. This isn't a big burden and it is unavoidable, so I am closing this bug.