yes, this is a mandatory requirement. the steps are:
- provide a subsystem implementation
- expose the management aspect through the common as7 layer
- build the console UI for it, that does leverage the above
/Heiko
On Mar 5, 2012, at 9:41 PM, Pedro Igor Silva wrote:
Hi Jason,
So we have to work first in a subsystem for PicketLink and then build the console to
integrate with it. Just like the AS 7 console, right ?
Regards.
Pedro Silva
----- Original Message -----
From: "Jason T. Greene" <jason.greene(a)redhat.com>
To: "Andrig Miller" <anmiller(a)redhat.com>
Cc: jboss-as7-dev(a)lists.jboss.org, "Anil Saldhana"
<Anil.Saldhana(a)redhat.com>
Sent: Monday, March 5, 2012 3:32:36 PM
Subject: Re: [jboss-as7-dev] PicketLink Console and AS7 Console
On 3/5/12 11:36 AM, Andrig Miller wrote:
>> From a usability perspective, one of our Andiamo issues/goals was
>> to consolidate consoles.
>
> So, we should NEVER create a new console, and everything should be in
> the one AS management console. So, we need to get Pedro working with
> Heiko on getting this integrated in.
Another Andiamo requirement was that everything that is manageable in
one management interface (console) is manageable in all others
(HTTP/JSON, CLI, Native DMR, etc etc), and that domain/multi-node
management apply to all exposed features. This means that console
extensions *MUST* only interact with the management infrastructure via a
subsystem.
--
Jason T. Greene
JBoss AS Lead / EAP Platform Architect
JBoss, a division of Red Hat
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev