[jboss-as7-dev] Subsystem specific deployer configurations in standalone.xml/domain.xml

[Brian Stansberry]

This UI issue is an argument against ever trying to extend the use of 
these configuration elements to cover a broad subset of what is included 
in deployment descriptors.

AIUI, the problem is not all of the options exposed by subsystems will 
be relevant to a given deployment. That is much less of an issue if the 
number of exposed options is quite small. For example, the actual use 
cases we have identified are the OSGi start policy, the OSGi start level 
and perhaps some things related to only deploying when a server becomes 
an HASingleton master. That's comprehensible even if the options are 
irrelevant to a particular deployment.

The distinction I see between these two use cases that are driving these 
new management model elements and what is in the deployment descriptors 
is that the latter are concerned with how the runtime services installed 
by the deployment are and how they behave, while this new stuff is about 
how the management layer treats the deployment -- what the criteria are 
that result in the deployment being processed.

I doubt that that's a totally clear black and white distinction, but if 
we restrict these new management model elements to the "how does the AS 
manage this deployment" side of the line, I think we'll be better off.

On 10/23/12 1:57 AM, Heiko Braun wrote:
>
>
> 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 at jboss.com
> <mailto:thomas.diesler at 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?
>


-- 
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat