Thursday Nov 12, 2015
Thursday Oct 29, 2015
By Annie Hayflick-Oracle on Oct 29, 2015
Cloud Services for Developers
I sat in today on an engaging session with Java EE expert David Blevins, who is a newly crowned Java Champion for his work in Open Source and Java EE for more than 10 years. As a member of the EJB, CDI, JMS, Java EE Security JSRs, and Java EE 6, 7 and 8 Expert Groups, he’s worked hard to make Java EE as simple, testable and lightweight as Java SE.
The next Java EE 8 edition, due in 2017, will focus on HTML5, cloud enablement, use of the model-view-controller framework and improved security. Another important selling point will be ease of use, which was the theme of much of Blevins's talk.
According to Blevin, the first era of Java EE was XML-driven where we used "tons and tons of deployment descriptors." The second era of Java EE, brought about by Java 5, was annotation-driven and very declarative by nature. With the advent of Java 8 features such as lambdas and method references, "we'll have the opportunity to take a look at all the Java EE APIs again and rewrite them to fundamentally reduce the ceremony we have to deal with when we write applications," he said. "I have some predictions: Java EE will shift from declarative to the programmatic since annotations are very declarative approach. With lambdas and method references, the approach is more to do it all at runtime."
He walked through a code example that highlighted a security example where one EJB was annotated as a Manager and another as Employee. "With lambdas and method references, you'll be able create a Manager EJB and an Employee EJB, and to test and run your code under many different security identities."
The impact of these kinds of capabilities in the new Java EE release means that there will be a shift in emphasis in Java EE programming from the Component-side to the Caller-side and that logic will become more mobile, Blevin concluded.
He also said that Java Community Process is a now an open process, which it wasn't a few years ago, and developers can now have an open say in the Java EE specification in JSR 366.
"If you don't vote, don't complain."
Thursday Sep 24, 2015
By Yolande Poirier-Oracle on Sep 24, 2015
Wednesday Sep 09, 2015
By Yolande Poirier-Oracle on Sep 09, 2015
Tuesday Sep 01, 2015
By Yolande Poirier-Oracle on Sep 01, 2015
Want to learn the intricacies of the new Java 8 Date and Time API? Learn how to simplify your programming of date and time and use Java 8 Date and Time API. In the next VTS, Simon Ritter discusses how the previous APIs treated the date and time and explains the much need improvements of the new API. For example, the classes java.util.Date and SimpleDateFormatter were not thread-safe.
Java 8 introduced the JSR 310, Date and Time API, which is based on the very popular open source Joda time API. The new Java library handles the format and schedule of time and date in a much more intuitive and flexible way. Simon explains in detail how to use the new API with different formats for setting future dates, dealing with time zones, adding temporal adjustors and much more.
VTS is a series of interactive online events with hands-on sessions and presenters answering technical questions. The events are sponsored by the Oracle Technology Network (OTN). They are free events but you must register. Join the next exclusive events near you:
- Americas - September 16th- 9:30am to 12:30 PST - Register
- EMEA - September 23rd - 9:30am to 12:30pm BST - Register
- APAC - September 30th- 3pm to 6:30pm AU/SYD - Register
Wednesday Jul 08, 2015
By Yolande Poirier-Oracle on Jul 08, 2015
Tuesday May 12, 2015
By Yolande Poirier-Oracle on May 12, 2015
- 10 December 2015: Feature Complete
- 04 February 2016: All Tests Run
- 25 February 2016: Rampdown Start
- 21 April 2016: Zero Bug Bounce
- 16 June 2016: Rampdown Phase 2
- 21 July 2016: Final Release Candidate
- 22 September 2016: General Availability
- JEP 200: defines a modular structure for the JDK.
- JEP 201: reorganizes the JDK source code into modules, enhances the build system to compile modules, and enforces module boundaries at build time.
- JEP 220: restructures the JDK and Java runtime environment (JRE) images to accommodate modules and to improve performance, security, and maintainability.
Wednesday May 06, 2015
By Yolande Poirier-Oracle on May 06, 2015
Register now. The event is free
Tuesday Apr 28, 2015
Thursday Apr 23, 2015
By Yolande Poirier-Oracle on Apr 23, 2015
Check out product manager Aurelio Garcia Ribeyro’s blog about Understanding Time Zone Udpater 2.0 to fully understand how to update to daylight saving time.
The security baselines for the Java Runtime Environment (JRE) at the time of the release of JDK 8u45 are specified in the following table:
JRE Family Version JRE Security Baseline
(Full Version String)
Java 8 1.8.0_45
Java 7 1.7.0_79
Java 6 1.6.0_95
Java 5.0 1.5.0_85
For more information about security baselines, see Deploying Java Applets With Family JRE Versions in Java Plug-in for Internet Explorer.