kedar wrote:
> If we change the "names" of the default profiles that
> are bundled with the product, then this would have to
> change. But the idea is that going ahead, if this feature
> is liked by developers/administrators, they can actually
> ask us to take the "default-config" from a particular profile.
>
> So, I do think that accepting the name of the profile is
> a good idea and makes the code flexible. It's just that
> for GlassFish V2, admin console sends in a profile name
> which is "cluster" (or whatever we decide). Going ahead, it
> might present you a list of profiles that are available
> to choose the default-config from. Again, the reason is
> that the default-config might be different for different
> profiles.
It's just weird that part of what this button does is wired
into the code, and the other part is taken from a profile template.
Allowing me to select among multiple templates isn't a completely
general solution, and it's not clear that it would always make
sense.
If we had a general "modify the current domain to be like the selected
domain" button, that would be cool, but a lot of work. I thought this
button had limited scope, just "modify the current domain to support
clusters".
And hopefully in the future we'll eliminate the need for the button,
so there would be little reason to generalize it.