I think this is where the description I've asked for comes into play.
If these parameters can be extracted from the DMR model (similar to :read-resource-description or part of that), then the tools (CLI, GUI) might provide two things:

a) request these parameters when deployments are "add'ed", i.e. an additional step when applications are  deployed from the console

b) extend the subsystem specific deployment views to show these settings as well

But I am not sure if we can easily provide a), because the affected subsystems are not know until the deployment content is actually moved from the repository to the server and processed by the deployment layers.

On Oct 23, 2012, at 6:40 AM, Thomas Diesler <thomas.diesler@jboss.com> wrote:

Ragarding the representation of these properties on the management UIs ...

I'm not clear on how this is supposed to work. Currently, the properties are modeled on the ADD operation. From the UI perspective there is no notion of target subsystem nor deployment type. How does the UI decide which properties are available in the context of a given ADD operation.

Lets take the auto-start and start-level props as an example.
How would this look like in the GWT console and on the CLI?