Not necessarily. Everything in the end speaks the underlying management
API. But that doesn't mean the syntax needs to be the raw dmr or json
This is primarily about UX and parsing. If we supported CLI syntax
there's no requirement to also parse basic DMR. The CLI itself doesn't.
If we support CLI syntax though it seems logical to use the CLI libs
themselves to do it. Otherwise we are maintaining two code bases for the
same thing. (I doubt the CLI parsing code can easily be extracted out
for reuse, although I may be wrong.)
On 9/4/14, 2:05 AM, Heiko Braun wrote:
2) builds on 3), right?
On 04 Sep 2014, at 06:16, Stuart Douglas <sdouglas(a)redhat.com
> 2) Allow the user to provide CLI commands to customise the server
> This is by far my favorite approach. The provisioning file would just
> contain a list of CLI commands, and would execute them in order. I think
> this is by far the most intuitive, and the CLI is well documented.
> 3) Allow the user to provide DMR operations to customize the server
> Similar to 2, but allow the user to provide DMR or JSON operations to
> customize the server. I think this is not nearly as nice as 2, as users
> are much more likely to be familiar with the CLI rather than DMR.
wildfly-dev mailing list
Senior Principal Software Engineer
JBoss by Red Hat