Bug 677916 - Make configuration components UI renderring overrideable at runtime
Summary: Make configuration components UI renderring overrideable at runtime
Status: NEW
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI
Version: 4.0.0.B02
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact: Mike Foley
Depends On:
TreeView+ depends on / blocked
Reported: 2011-02-16 09:34 UTC by Lin Gao
Modified: 2020-04-27 01:17 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed:

Attachments (Terms of Use)
screen shot for the jca config-properties configuration list (85.44 KB, image/png)
2011-02-21 08:24 UTC, Lin Gao
no flags Details

Description Lin Gao 2011-02-16 09:34:53 UTC
This is a feature proposal:

In the resource configuration:

 <c:list-property name="config-property">
     <c:map-property name="config-property">
       <c:simple-property name="name" readOnly="true" />
       <c:simple-property name="value" />

in some cases, some of the 'value' properties need to be read only, others do not. 
In the case of JCA 1.6, it depends on the config-property`s dynamic attribute value(true or false).

In current implementation, UI rendering is pre-defined in the rhq-plugin.xml, and can not be changed at runtime.

Use case comes from the discuss: http://community.jboss.org/thread/161336

Please refer to the mail list thread: https://fedorahosted.org/pipermail/rhq-users/2011-February/000319.html

Comment 1 Lin Gao 2011-02-21 07:45:10 UTC
RHQ doesn't support dynamic resource plugin metadata, so that it can not decide how to render the configuration UI components at runtime.

The use case mentioned in the community discuss: http://community.jboss.org/message/586549#586549 requires RHQ to have a ability to override the configuration definition in build-time resource plugin metadata, so that it can change the configuration component UI component`s attributes at runtime.

Comment 2 Lin Gao 2011-02-21 08:24:07 UTC
Created attachment 479840 [details]
screen shot for the jca config-properties configuration list

Comment 3 Lin Gao 2011-02-21 08:32:17 UTC
For example:

In the following configuration definition:

  <c:group name="ConfigProperties" displayName="All Config Properties">
    <c:list-property required="false" name="config-property" readOnly="true">
        <c:map-property name="config-property">
            <c:simple-property name="name" readOnly="true" />
            <c:simple-property name="type" readOnly="true">
                    <c:option value="java.lang.String"/>
                    <c:option value="java.lang.Boolean"/>
                    <c:option value="java.lang.Integer"/>
                    <c:option value="java.lang.Double"/>
            <c:simple-property name="value" required="false" />

The simple-property of 'value' here is not defined as read only, and please refer to the attached screenshot:config-properties.png, in this case, the property name: 'LTMCFPropIntegerOne' should be read only, which is a requirement of JCA 1.6; the property name: 'MyConfidentialProperty' needs to be displayed as: '*****', which is a requirement of JCA 1.6 also.

But currently, all these config properties are not read only and displayed as plain text. We need RHQ to support that.

Note You need to log in before you can comment on or make changes to this bug.