On 2/14/11 11:35 AM, Heiko Braun wrote:
On Feb 14, 2011, at 6:18 PM, Brian Stansberry wrote:
>>>
>>> I think we should proceed on the assumption that it won't be possible to
>>> have a subsystem configured which has a dependency on another subsystem
>>> which is missing.
>>
>> Yes, but to build tooling around that (web UI), I would need to know subsystem
interdependencies upfront.
>> (i.e. meta data). Otherwise I cannot put this feature into the console.
>>
>
> Is that really a requirement, i.e. making things foolproof? I totally
> agree it's highly desirable and something we should see if we can
> improve, but is it a requirement? If people are trying to add profiles
> (or subsystems) to running domains via the web UI, they are either going
> to be in dev mode or they've tested what they are doing in advance.
I completely agree. But for this exact reason I would say it doesn't even need to be
possible through the web UI.
IMO we can easily consider this out of scope.
Haha, I have to do better at getting my head fully out of core API mode
and into web UI mode. So, I agree; just because the core management API
makes something possible doesn't mean there has to be a polished GUI for
it. We need to allow adding profiles in the core API, otherwise to add a
new profile to a domain users would have to down the DC, edit domain.xml
and restart DC. The web UI is a whole different animal.
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat