[jboss-jira] [JBoss JIRA] (WFWIP-324) Bootable JAR - Add an alternative way to the CLI in order to configure the server

[Darran Lofthouse (Jira)]

    [ https://issues.redhat.com/browse/WFWIP-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14351705#comment-14351705 ] 

Darran Lofthouse commented on WFWIP-324:
----------------------------------------

I was questioning something similar myself.

Galleon in itself is not a configuration tool, it is a tool to assemble "layers" of functionality into a running server making a defined set of features available.  Configuration creeps in a bit as we need things like selecting between legacy security and Elytron security, but anything beyond that is not what Galleon and the layers were intended to solve.

As an example I am contributing an example to the bootable jar project to enable username / password authentication for a deployment - at the moment this will lead to numerous CLI commands to achieve but it feels like there may be a middle ground of common tasks / use cases that could fit somewhere between layers and CLI scripts.


> Bootable JAR - Add an alternative way to the CLI in order to configure the server
> ---------------------------------------------------------------------------------
>
>                 Key: WFWIP-324
>                 URL: https://issues.redhat.com/browse/WFWIP-324
>             Project: WildFly WIP
>          Issue Type: Enhancement
>            Reporter: Fabio Burzigotti
>            Assignee: Jean Francois Denise
>            Priority: Major
>
> Using the CLI to configure the packaged server seems not to be the optimal or final solution, since it reveals implementation details about the runtime and its usage is not immediate.
> Furthermore that configuration makes POM definition more cumbersome IMHO.
> This WFWIP is to discuss an enhancement as an alternative to the CLI scripts for a static configuration of the server.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)