Find JSRs
Submit this Search

Ad Banner

JSRs: Java Specification Requests
JSR 373: JavaTM EE Management API 2.0

Open Nominations

Nomination Type Full Name Biography Spec Lead Comments Submission date Spec Lead Vote PMO Vote

Approved Nominations

Nomination Type Full Name Biography Spec Lead Comments Submission date Spec Lead Vote PMO Vote
Expert Group Fabian Stäber Dr. Fabian Stäber is a senior software developer, architct, consultant, lead of the research and development unit at ConSol* Consulting & Solutions Software GmbH. He has been developing Java Server applications for about 15 years. Fabian is an active member of the Java community, gives talks at developer conferences, and writes publications for developer magazines. His academic background is on peer-to-peer computing in industrial applications. Mar 12, 2015 Y Y
Expert Group Adam Bien Consultant and author Adam Bien is an Expert Group member for the Java EE 6 and 7, EJB 3.X, JAX-RS, and JPA 2.X JSRs. He has worked with Java technology since JDK 1.0 and with Servlets/EJB 1.0 and is now an architect and developer for Java SE and Java EE projects. He has edited several books about JavaFX, J2EE, and Java EE, and he is the author of Real World Java EE Patterns—Rethinking Best Practices and Real World Java EE Night Hacks—Dissecting the Business Tier. Adam is also a Java Champion, Top Java Ambassador 2012, and JavaOne 2009, 2011, 2012 and 2013 Rock Star. Adam occasionally organizes Java EE workshops at Munich’s airport ( Feb 9, 2015 Y Y
Expert Group Chris Vignola Chris Vignola is the architect/designer for IBM WebSphere Application Server systems management. Chris has developed Java EE technology for 15 years. He is the current IBM owner of J2EE Management and JMX implementations. Feb 5, 2015 Y Y
Expert Group Kabir Khan I joined JBoss in 2004 before the 2006 Red Hat acquisition. I have led the JBoss AOP project, and contributed to our original EJB 3 implementation. I later joined the JBoss Microcontainer team, which was the core of JBoss 5 and 6, before joining JBoss AS 7 (now called WildFly) in 2010 in the very early days of the project. Our supported offering, JBoss EAP 6.x, is based on AS 7/WildFly. I have focussed on our server management and deployment capabilities, which are very relevant to this JSR. I also wrote our current JSR 77 implementation. Jan 19, 2015 Y Y
Expert Group Roland Huss My name is Roland Huss and I'm working for a Software Company called "ConSol" locate in Munich, Germany, I have a working experience in Java for 17 years as Developer and Software architect. Also, I'm the author of Jolokia [1], a utility which allows JMX access via HTTP and JSON with a REST-like interface. My LinkedIn Profile can be found at [6]. Jolokia exists now for more than 5 years and I could collect quite some real world experiences about remote monitoring/management with HTTP and JOSN on the way. Some new concepts like bulk requests (many queries with a single HTTP request) help tremendously when monitoring many attributes on thousands of servers. Jolokia is currently the de-factor standard for monitoring Java Servers with HTTP and is used in many Open Source products as a remote management API: - ActiveMQ [2] uses Jolokia as remote management access since 5.7 - Spring Boot [3] includes Jolokia as a feature. - [4] uses Jolokia extensively and exclusively for accessing any Java based backend system (for both management and monitoring) - OSv [5] uses it as its management API Also, I'm a big supporter of JSR-77 and in having a common naming scheme for monitoring (although the real 'meat', namely providing statistics was never seriously picked up by JEE Servers in the past (except Websphere ...)). Hence I really would like to help to further evolve this standard and to contribute. [1]: [2]: [3]: [4]: [5]: [6]: Nov 28, 2014 Y Y
    Spec Lead Vote Legend:
    -Not yet reviewed/pending - The Spec Lead has not processed this nomination
    PProcessing - The Spec Lead has seen the nomination and needs more time to arrive at a decision
    NNo - The Spec Lead has decided that this nominee should not be on the JSR
    YYes - The Spec Lead wants the nominee on the JSR

    PMO Vote Legend:
    -The PMO has not yet voted on this nomination
    PProcessing - The nominee can not yet participate on this JSR, but the legal agreements are being processed
    IIncomplete, Illegible, or Inaccurate nomination
    XAMissing required agreement to participate on this JSR - Addendum (ECA) Required
    XMMissing required agreement to participate on any JSR - Not a JCP Member
    XNot able to be on a JSR - The PMO has determined that this person cannot be on this JSR
    YYes - The PMO views this as a valid nomination with a current Membership in place