GWT config editor question
Jay Shaughnessy
jshaughn at redhat.com
Thu Jun 9 13:41:41 UTC 2011
Oh, something more like dynamic config defs. That's kind of wild.
Would there be default values or would it always be dynamically
resolved? One idea that comes to mind is to make the expression very
naturally oriented towards criteria search.
It may make sense to pass a "dynamic" config def back to the server for
realization, returning back a non-dynamic config-def and then pass that
into the config editor.
On 6/9/2011 9:18 AM, Heiko W.Rupp wrote:
> I think I need to explain this a bit better
>
> I will have a definition like (just a first draft idea)
>
> <c:simple-property name="prop2">
> <c:property-options>
> <c:source target="resource"
> linkToTarget="true"
> filter="*.jdbc"
> expression="resourceType=DomainDeployment,resource=*" />
> </c:property-options>
> </c:simple-property>
>
> where the property-options do not come from a fixed list, but from a resolver
> that takes the given expression to locate matching resources (in this case
> all resources of resource type DomainDeployment and then filters the resulting
> entries found by a name filter for resources where the name ends in .jdbc.
> This list is then supposed to show up in a config editor as a drop down listing
> all the available jdbc drivers to choose from.
>
> Heiko
>
More information about the rhq-devel
mailing list