On 29 Apr 2013, at 13:47, Alan Santos <[email protected]> wrote: > > On Apr 29, 2013, at 8:45 AM, Tristan Tarrant <[email protected]> wrote: > >> On 04/29/2013 02:39 PM, Manik Surtani wrote: >>> On 29 Apr 2013, at 11:29, Tristan Tarrant <[email protected]> wrote: >>> >>>> On 04/29/2013 11:56 AM, Manik Surtani wrote: >>>>> On 29 Apr 2013, at 10:28, Tristan Tarrant <[email protected]> wrote: >>>>> >>>>>> Dear all, >>>>>> >>>>>> I am about to create a new project under the Infinispan GitHub umbrella: >>>>>> infinispan-server-console. >>>>>> This will be an extension to the standard AS/EAP console that allows >>>>>> configuration and management of the remote protocol endpoints. Currently >>>>>> the code is very simple and doesn't do much, but hey, release early >>>>>> release often. >>>>> As in, the GUI console? >>>>> >>>> The very same. >>> Why do we need this? Isn't it duplication of functionality that JON/RHQ >>> provides? >> JON/RHQ give you a mostly read-only interface (attributes) and commands >> (operations), but it doesn't really give you a flexible way to modify >> the configuration (creating caches, adding cache stores, adding >> endpoints, etc) > > > Why not? That's probably the top requested feature for the JON plugin.
Right. I'd rather we enhance the JON/RHQ plugin to do this rather than to start on Yet Another Console. Are there any limitations to enhancing the JON/RHQ plugin? - M -- Manik Surtani [email protected] twitter.com/maniksurtani Platform Architect, JBoss Data Grid http://red.ht/data-grid _______________________________________________ infinispan-dev mailing list [email protected] https://lists.jboss.org/mailman/listinfo/infinispan-dev
