[#RHQ-221] Weird configuration caching on resource create

RHQ Project

Weird configuration caching on resource create

Created: 02/Apr/08 10:51 AM Updated: 06/Oct/08 09:15 PM

Component/s:

FX - Inventory

Affects Version/s:

0.1

Fix Version/s:

1.1

Time Tracking:

Not Specified

Issue Links:

Relation

This issue Relates To:

~~RHQ-222~~ Resubmitting a failed configuration-backed resource create results in locked attributes

Resolution Date:	30/Sep/08 04:04 PM
Date of First Response:	29/Sep/08 04:35 PM
Tester:	Jeff Weiss
VCS Revision:	1,656

Description

« Hide

To replicate:

- Attempt to create a new JMS queue. Use the same JNDI name as an existing queue so the request fails.
- Navigate back to the resource's Inventory tab.
- Use the drop down to select JMS queue again under Create New.

The configuration will be auto-populated with the same values as the last attempt to create a queue.

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Jason Dobies - 02/Apr/08 10:52 AM

Additionally, the JNDI name is not editable. This is likely due to it being marked as read only in the configuration definition:

[11:51] <joseph> perhaps, but i'm think what happens is that it's now looking it up with the config def for that resource type, which marks that field as readonly

[ Permlink | « Hide ]

Jason Dobies - 02/Apr/08 10:55 AM

Keep in mind this is more serious than ~~RHQ-222~~. I was unable to create another JMS queue after my first attempt, even though I was going through the Create New interface. Since the JNDI name was uneditable, I was completely unable to create the second JMS queue after this occurred.

[ Permlink | « Hide ]

Jay Shaughnessy - 29/Sep/08 04:35 PM

~~RHQ-221~~/222 Add support for fully editable configurations. Prior we could support the ability to edit existing values for readonly properties. But this is necessary when still performing a resource create after a failed submit." --username "jshaughn"

This fix may have also been helped by changes made for rhq-897.

[ Permlink | « Hide ]

Jeff Weiss - 30/Sep/08 09:55 AM

<jweiss> jshaughn: http://jira.rhq-project.org/browse/RHQ-221 - fixed that particular case, but if you click "Resubmit", "Cancel", then try to create new, it still gets populated with the values on the Resubmit page.
<jshaughn> ok, kick back 221. 222 should be fixed.

To clarify how to reproduce, do the original repro steps, then in the JBossMQ Inv page, click "Resubmit" on the failed resource create. Then "Cancel", then create a new JMS Queue again. Note the values are pre-populated with the old values when they should be blank.

[ Permlink | « Hide ]

Jay Shaughnessy - 30/Sep/08 04:04 PM

clear the config on create cancel. And related work in ~~RHQ-222~~, embed the isFullyEditable check in the isReadOnly check for ConfigUIComponent.

[ Permlink | « Hide ]

Jeff Weiss - 06/Oct/08 09:15 PM

Values are no longer held when you resubmit/cancel/create. rev1712