Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Java EE Transparent Enough?

DZone's Guide to

Java EE Transparent Enough?

· Java Zone
Free Resource

Are you joining the containers revolution? Start leveraging container management using Platform9's ultimate guide to Kubernetes deployment.

Grassroots level community participation is key to the success of any open standard - Java EE is certainly no exception. Realizing this fact, Oracle (and Sun before it) has done quite a bit to improve transparency through the ongoing process of JCP reform. The improvements are pretty clear to those of us working with the JCP for a number of years, especially as independents. The changes are not necessarily obvious to folks new or unfamiliar with the JCP however. In fact, many still seem to hold some pretty dubious views on the JCP.

My colleague Arun Gupta recently wrote a very insightful blog on this topic titled Transparency and Community Participation in Java EE 7. It's definitely a worthwhile read and a great place to start if you are curious about the JCP or are interested in participating yourself. In the blog entry, Arun discusses some of the crucial changes in JCP 2.8, how Java EE 7 JSRs have met and exceeded the transparency requirements, including some hard data on improved community participation as well as the outstanding continued success of initiatives like Adopt-a-JSR via JUGs worldwide.

Using Containers? Read our Kubernetes Comparison eBook to learn the positives and negatives of Kubernetes, Mesos, Docker Swarm and EC2 Container Services.

Topics:

Published at DZone with permission of Reza Rahman, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

THE DZONE NEWSLETTER

Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

X

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}