[jboss-dev-forums] [Management Development] - Profiles in domain.xml

[Alexey Loubyansky]

Alexey Loubyansky [http://community.jboss.org/people/alex.loubyansky%40jboss.com] replied to the discussion

"Profiles in domain.xml"

To view the discussion, visit: http://community.jboss.org/message/546490#546490

--------------------------------------------------------------
> Scott Stark wrote:
> I still think the best comprimise would be to have profile definitions in the domain in terms of the required capabilities potentially simplified by having implied capabilities associated with each application type that could be overriden by the admin.

Ok, this makes sense. Taking it further... The profiles in the domain schema (as they are now) are kind of redefined, i.e. it's not the same profile definition/configuration as the actual profile configuration like here  http://community.jboss.org/wiki/AS6ServerSideConfiguration http://community.jboss.org/wiki/AS6ServerSideConfiguration

So, I want to clarify the purpose and meaning of this redefinition in the domain config. Perhaps, it also makes sense to choose a different name not to confuse with the actual profiles.
I think if we can make domain.xml contain only the concepts/notions that are defined in its schema, it would be the best. I.e. if it contained (was expressed in) only the terms defined for it and learning additional concepts/notions for the user wouldn't be a requirement to understand the configuration.

Can we think about the profiles here as a set of capabilities that might be activated once there is an application requiring them? I.e. not to think about them as defining capabailities that must be activated after the start-up?
Perhaps, something like "environment" would describe it?

So, what I think we can do:
- define a set of implied capabilities associated with each application type (or define the "environment" for each application type);
- if an application is mentioned in the domain.xml w/o specified by the admin "environment" it requires, we assume our defaults;
- if the admin wants to be precise, it could look like
  <application name="" path="">
    <environment name=""/>
    <environment-ref name=""/>
  </application>

- there could be a section in the domain config where the admin can define his own named environments and reference them later for applications.

Then actually the set of applications mentioned in the domain.xml will dictate (through their "environments") which profiles/subprofiles to activate and run.

Does it make sense?

--------------------------------------------------------------

Reply to this message by going to Community
[http://community.jboss.org/message/546490#546490]

Start a new discussion in Management Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2107]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-dev-forums/attachments/20100607/c2afb2b2/attachment.html