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

Key: RHQ-580
Type: Bug Bug
Status: Accepted Accepted
Priority: Major Major
Assignee: Unassigned
Reporter: John Mazzitelli
Votes: 0
Watchers: 0
Operations

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

support allowCustomValue - it isn't implemented right now

Created: 15/Jun/08 07:55 PM   Updated: 19/Jul/08 03:23 PM
Component/s: Plugin Container
Affects Version/s: 1.0.1
Fix Version/s: None

Time Tracking:
Not Specified

Date of First Response: 15/Jun/08 08:08 PM


 Description  « Hide
In the <configuration> section of a plugin descriptor, you can specify <property-options>

<simple-property name="databaseType">
<property-options>
    <c:option value="mysql"/>
    <c:option value="oracle"/>
    <c:option value="postgres"/>
</property-options>
</simple-property>

The schema for <property-options> also defines an "allowCustomValues" attribute. If true, this is supposed to render a text box above the hard-coded selections to allow the user to enter a text value for a custom value (in the example above, in order for me to allow the user to select "sybase", I would need to do this:

<property-options allowCustomValue="true">
...

This allowCustomValues isn't implemented. To implement it, it requires the config UI to be coded up to support that value.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Joseph Marques - 15/Jun/08 08:08 PM
fair enough. hopefully, in your case, if you only have a single option you need to add, you'll be able to just extend this and just hard-code <c:opton value="sybase" /> for now...which I'm sure you've already done by now. ; )