History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: RHQ-495
Type: New Feature New Feature
Status: Accepted Accepted
Priority: Major Major
Assignee: Unassigned
Reporter: Ian Springer
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
RHQ Project

allow user to specify Resource names for new Resources prior to or at the time of import

Created: 16/May/08 07:59 AM   Updated: 13/Oct/08 03:37 PM
Component/s: Plugin Container, Core UI, Core Server
Fix Version/s: None

Time Tracking:
Not Specified

Date of First Response: 17/May/08 09:57 PM


 Description  « Hide
A couple possible ways to do this:

1) On the dashboard autodiscovery portlet, add an input box for the name of the Resource. When the Import button is clicked, the specified name will be used.
2) Add a 'defaultName' plugin config prop to any Resource types that we want the user to be able to control the default name. Note, to make this option viable, we will need to add a way for users to edit the plugin config templates.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Joseph Marques - 17/May/08 09:57 PM
yes, this was something i wanted to do in 1.x back when there were all those patches to make the jbas and tomcat names more unique. but the plugin configuration code was messy back then.

now, with 2.0, this is actually possible. ideally, i'd love to see plugin config templates, and then expose certain constructs to the user with an ordered list of well-known tokens to choosen from to build up the name.

this would, for instance, present the user with the following list for a JBAS instance:

platformName
resourceType
resourceVersion
configSet
bindAddress
bindPort
partitionName
custom

which users could then choose in an ordered way like:

${platformName} ${resourceType} ${resourceVersion} ${configSet} (${bindAddress}:${bindPort})

and then parameter replacement might create something like:

marques-custom JBossEAP 4.3.0.GA production (172.16.1.1:1099)

choose a different ordering:

${partitionName} ${platformName} (${bindAddress}:${bindPort})

and you get:

EAP43-cluster marques-custom (172.16.1.1:1099)

Joseph Marques - 17/May/08 09:59 PM
the replacements would be listed in the type definition inside of rhq-plugin.xml and the plugin impl would somehow have to supply values for these. this way, each plugin could optionally implement this name-switching interface, and then be able to arbitrarily configure names for those typed resources via the web console.

Charles Crouch - 08/Sep/08 10:44 AM
This originated in case 159585