Find JSRs
Submit this Search


Ad Banner
 
 
 
 


Profiles of JCP EC Representatives

 
 
The job of an Executive Committee (EC) representative is a serious commitment. The time required is extensive, and includes reading of specifications, Reference Implementations (RIs), and Technology Compatibility Kits (TCKs), as well as regular attendance at EC meetings and teleconferences to discuss and vote on various technical and process topics. Besides voting on Java Specification Requests (JSRs) at various stages, the EC guides the Program Management Office (PMO) in the evolution of the Java Community Process (JCP) program. EC decisions can have significant, long-term consequences to not only the community, but also in the industry and the market. Still, plenty of JCP participants relish the task of representing a corporation, non-profit, open source group, or themselves.

Mark Little
In keeping with a commitment to develop software in the Professional Open Source model that is compliant with all relevant standards, Red Hat Middleware LLC joined the JCP program in September 2003 and was nominated for the JCP Member of the Year award in 2006. Red Hat believes standards must be developed in an open manner, with strong community participation. 26 Red Hat members live up to that premise, with energetic involvement in the development of approximately 24 JSRs addressing a wide range of technologies such as Enterprise JavaBeans 3, Java Enterprise Edition 5, and Web Services. Red Hat individuals provide the kind of vigorous developer and user feedback that is critical to the continued success of the JCP program.

 
Dr. Mark Little serves on the SE/EE EC as the primary representative of Red Hat. He is the SOA (Service-Oriented Architecture) Technical Development Manager and Director of Standards in the JBoss division. Before joining Red Hat, Mark was Chief Architect and co-founder at Arjuna Technologies, a spin-off from Hewlett-Packard. He says, "My main goal is to work on improving the openness of the JCP program and increasing adoption of Java EE."

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .