jsr342-experts@javaee-spec.java.net

[jsr342-experts] Re: Pruning JSR-77

From: Jason T. Greene <jason.greene_at_redhat.com>
Date: Mon, 07 Nov 2011 16:01:41 -0600

On 11/7/11 11:25 AM, Adam Bien wrote:
>
> On 10.10.2011, at 19:59, Bill Shannon wrote:
>
>> Jason T. Greene wrote on 10/10/11 7:25 AM:
>>> We skipped pruning JSR-77 last time around because a number of us thought it was
>>> better to update it to be more current. I think it's become clear that the spec
>>> is not only not going to be updated, but that its relevance is fading with the
>>> cloud direction the industry is moving in.
>>
>> I agree, we're not expecting significant updates to JSR-77, and we need a
>> different management API in the long term. I'd be much happier if we had
>> a replacement in place when we make JSR-77 optional.
> +1 the good thing about JSR-77 is that it forces the application server to expose a consistent set of monitoring data.
> It is a major added-value over e.g. Plain Old Web Container...

I'm not sure it does that with so much of the spec being optional.

-- 
Jason T. Greene
JBoss AS Lead / EAP Platform Architect
JBoss, a division of Red Hat