Bug 814309

Summary: Create Child Resource - allow for pre-computed target resource names
Product: [Other] RHQ Project Reporter: Heiko W. Rupp <hrupp>
Component: Core UIAssignee: RHQ Project Maintainer <rhq-maint>
Status: NEW --- QA Contact: Mike Foley <mfoley>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 4.3CC: hrupp
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Heiko W. Rupp 2012-04-19 10:48:23 EDT
For Bug 813214 only resource names that are defined at a different type are allowed, as the names indicate which other resource to override.

It should be possible in the create child resource wizard to use expression like this in <c:option-source> to pre-populate the name box with propsals.

      <c:simple-property name="baseDefinition" required="true" readOnly="true" description="The definition from host level to use/override">
        <c:option-source target="resource" expression="type='JVM Definition (Host)' plugin=jboss-as-7"/>

In other cases it may be possible that the user can not choose a name at all - here one could also skip the first page of the wizard with the name and directly go to step2
Comment 1 Charles Crouch 2012-04-19 11:14:49 EDT
(10:12:29 AM) pilhuhn: The docs bug 814312 describes the current implementation ,so that sunny-dee can put warnings in the docs, that the user given name is not honored and that if the user tries to create a 2nd resouce of the singleton resource type, he will get an exception saying so
(10:12:49 AM) ccrouch: so if 814305 is fixed, the doc issue becomes "don't worry about specifying a resource name, we create one under the covers"
Comment 2 Heiko W. Rupp 2012-04-19 11:25:50 EDT
[17:15:14] <pilhuhn> actually with '09 we can either skip the defined user name and pick from the baseDefinition on the next page
[17:15:26] <pilhuhn> Or put the baseDefinition selector on the naming page

For the user experience and also our implementation of plugin classes it is cleaner to not have to specify the name computation expression in the plugin config, but leave it on level of the 1st wizard page.
Comment 3 Mike Foley 2012-04-23 12:11:00 EDT
setting priority to medium per BZ triage 4/23 (crouch, santos, oleary, foley)