Yes, what Heiko describes was the rationale. It's not very satisfying
though. To switch a set of servers from one profile to another you have
to create a new server group, then delete the old servers and create new
matching ones that reference the new group.
There are plenty of config changes that can't be applied immediately to
a server runtime (e.g. adding or removing a subsystem that handles
deployment processing.) Those put the server in a "restart required"
state. We could handle these in the same manner. It requires a little
bit of extra work to implement, but I don't think it would be a big
deal. WDYT?
On 4/26/11 8:27 AM, Heiko Braun wrote:
I know. All I am asking for is some clarification how to move forward.
On Apr 26, 2011, at 3:20 PM, Heiko W.Rupp wrote:
>
> Am 26.04.2011 um 15:18 schrieb Heiko Braun:
>> same thing for server-group/profile
>>
>> bug or feature?
>
> I think that makes some sense. Changing the server-group or profile for a
> managed instance would be a major reconfiguration of it. Deleting and creating
> a new instance is probably much easier to handle and to get right.
>
> Heiko
>
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat