activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martyn Taylor <mtay...@redhat.com>
Subject Re: What is the current status and plans for the web-console?
Date Fri, 03 Mar 2017 11:47:10 GMT
Sounds like a great idea.  Cheers.

On Thu, Mar 2, 2017 at 3:37 PM, Christian Schneider <chris@die-schneider.net
> wrote:

> That sounds good. In the worst case we learned something in the best case
> we got the start of a good console.
>
> Christian
>
>
> On 02.03.2017 03:16, Clebert Suconic wrote:
>
>> What about this .....
>>
>>
>> I want to learn something knew :) and I want t a break after what I'm
>> doing
>> now.
>>
>>
>>
>> Let's try making a prototype around next month.  (April)
>>
>> If it gets too difficult we go back to the hawt io road.
>>
>>
>> ????
>>
>>
>>
>>
>> On Wed, Feb 22, 2017 at 2:56 PM Clebert Suconic <
>> clebert.suconic@gmail.com>
>> wrote:
>>
>> I liked Martyn's proposal for being a cool thing :)
>>>
>>>
>>> Just looked at this thing he mentioned (bootstrap).. man.. it's really
>>> cool...
>>> http://getbootstrap.com/getting-started/
>>>
>>>
>>> I'm not writing software just to be cool... but a great console would
>>> definitely improve things...
>>>
>>>
>>> One thing with a great UI though... our website still sucks :)
>>>
>>>
>>> - It provides a framework for plugins. So you can have one console that
>>>> gives you access to ActiveMQ but also to other modules in your system
>>>> - It uses jolokia to access the existing JMX layer over REST. So we do
>>>>
>>> not
>>>
>>>> need to create an additional REST layer for the console on the AMQ and
>>>> Artemis side
>>>> - Uses a html/javascript client (Angular). So the client side is easy to
>>>> install on any server
>>>>
>>>> So if we do not write a Hawtio plugin then we should still consider to
>>>>
>>> use
>>>
>>>> jolokia to avoid overhead on the server side.
>>>> I also think a framework to hook other plugins in would be great but for
>>>> just the activemq and artemis consoles it is not absolutely necessary.
>>>>
>>> +1... although I strongly encourage to keep the bits isolated. Not
>>> only for easy switch between AMQ5 and Artemis, but eventually we could
>>> include other technologies available on the console. (examples: AMQP
>>> Management, JMX, some consoles standard that I don't remember now, or
>>> any other thing yet to be invented)..   All I'm asking is for standard
>>> OO encapsulation.
>>>
>>> So ideally I would like to have something like Hatwio at apache as a
>>>>
>>> generic
>>>
>>>> base for a console where all apache projects can hook in via plugins.
>>>> Unfortunately this is a lot of effort and I am not sure if we find
>>>> enough
>>>> manpower to do it.  It would also be a project on its own and should not
>>>>
>>> be
>>>
>>>> done at activemq.
>>>>
>>>
>>>
>>> ..... if I had the time.....     :/
>>>
>>>
>
> --
> Christian Schneider
> http://www.liquid-reality.de
>
> Open Source Architect
> http://www.talend.com
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message