[wildfly-dev] Automatically resolving expressions in the CLI

Edward Wertz ewertz at redhat.com
Wed Jul 16 09:23:49 EDT 2014


The issue from a UX perspective is that resolving values against the host controller leads to uninformative failures or meaningless information. There's no sense in resolving an expression in a profile against the HC, if the expression is even in that JVM to be resolved, since the values on the servers aren't dependent on that at all. A user could leave that experience thinking they have accurate information about their servers when they actually don't.

I'd prefer the functionality to be disabled with an informative error message.

Joe


----- Original Message -----
> 
> 
> 
> 
> On Wed, Jul 16, 2014 at 5:40 AM, Edward Wertz < ewertz at redhat.com >
> wrote:
> 
> 
> However, the issue is how to limit it within the configuration tree.
> 
> 
> Why would you want to limit it?
> 
> 
> read-resource/read-attribute operation will be executed in right
> context anyway and .resolve() will work properly. (at least i think
> so)
> 
> 
> anyhow you can get what you are looking for with
> context.getRunningMode()
> 
> 
> --
> 
> tomaz
> 


More information about the wildfly-dev mailing list