There is a lot of concern of late surrounding Oracle’s commitment to Java EE. InfoQ broke the news last month in an article about the Java EE Guardians. Spring Data project lead Oliver Gierke at Pivotal expressed his thoughts on the potential impact to the Java community.
JSON-B, the JSON binding library expected to be added to Java EE 8, has been released for public review. The library builds on top of JSON Processing, and intends to provide a standard alternative to popular libraries like Jackson or Gson. The JSR is only targeted for inclusion Java EE though, meaning users of Java SE will still need to make use of external libraries.
The Java EE Guardians are a veritable who’s who of Java luminaries, including “Father of Java” James Gosling, former evangelists Reza Rahman and many other Java technorati. This news article covers their newly formed movement and important information on the charter.
Jinq, a library to provide a DSL for database queries, has been made available for Java and Scala. The work is inspired by .NET's LINQ, and aims at enabling easy-to-write queries with support for type safety. As commented by Ming-Yee Iu, creator of the tool, work on Jinq started in 2006 under project name Queryll; however, the adoption of lambdas in Java 8 is what has realised its full potential.
At the end of 2015 Steve Millidge from C2B2 and a co-founder of Payara predicted that 2016 would be the year of Java EE microservices. Many efforts would tend to agree, including WildFly, TomEE and the KumuluzEE framework. However, other developers believe that there are fundamental problems with Java EE which make it a poor choice for microservices.
InfoQ sat down with Markus Eisele, developer advocate at Red Hat, at the Devoxx BE conference, and asked about his thoughts on implementing microservice architectures within large-scale enterprise organisations. The conversation was primarily based on his recent O'Reilly mini-book publication, “Modern Java EE Design Patterns: Building Scalable Architecture for Sustainable Enterprise Development".
In preparation for JavaOne 2015, InfoQ held a Q&A session with a number of speakers at this year's conference that caught our eye.
JVM monitoring vendor Plumbr has added slow query detection to its flagship product. With this addition, Plumbr now detects four types of problems: Memory Leaks, Garbage Collection Inefficiencies, Locked Threads and Expensive JDBC Operations.
At JavaLand 2015, Ed Burns provided an overview of the Java EE Servlet 4.0 specification (JSR 369), the main focus of which is to introduce HTTP/2 support into the Java EE Platform. HTTP/2 aims to overcome problems with the existing HTTP specification, and new features include request/response multiplexing, binary framing, stream prioritisation, server push and header compression.
At JavaLand 2015, Arun Gupta presented several ‘recipes’ for deploying Java EE applications using Docker and Kubernetes. Gupta stated that containers are beneficial for deploying and managing applications, as they provide faster deployment, isolation and portability. The use of a container cluster manager, such as Kubernetes, also ensures availability and scalability.
The Java Community Process published details of JSR 375, a redesigned Java EE Security API that includes improvements for implementing security in a cloud environment.
Microsoft recently announced new machine learning capabilities for Microsoft Azure platform. Developers can also create their own web services and publish them to Azure Marketplace. Microsoft also announced availability of Apache Storm for Azure. Azure Stream Analytics, Data Factory and Event Hubs for Azure were all announced in the past few weeks by Microsoft. In this article we explore moreabout
Oracle execs discuss developments and roadmap in Java EE and Internet of Things
Oracle recently announced a JSR for MVC 1.0. JSR 371 was motivated by results of a Java EE 8 Survey, covered by InfoQ in March of this year. 61% of those surveyed supported the idea of providing support for an action-based MVC framework, alongside JSF. Only 26% felt there was an existing framework that could do the job, and 42% of those mentioned Spring MVC.
The recently released version v1.0.0 of HazelcastMQ adds a Java STOMP client and server implementation as well as an Apache Camel component. HazelcastMQ is a provider of a messaging layer on top of the basic Queue and Topic data structures in Hazelcast, an in-memory data grid. STOMP is the Simple (or Streaming) Text Orientated Messaging Protocol, an interoperable wire format.