
| Key: |
RHQ-495
|
| Type: |
New Feature
|
| Status: |
Accepted
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Ian Springer
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
| Date of First Response: |
17/May/08 09:57 PM
|
|
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.
|
|
Description
|
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. |
Show » |
|
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)