- JavaLand Conference Offers Thrills
- Free Open Source Tools for Maven, HTML5, IoT, and Java EE
- New Java Champions: Enrique Zamudio, Otávio Santana, and Freddy Guime
- New Java Champion: Jacek Laskowski
- Save the Date: 2015 JavaOne Brazil
- Java Magazine: Platform for Innovation
- NightHacking at Jfokus 2015
- A Young Woman Innovator Programs with Java
- Antoine Sabot-Durand Discusses CDI 2.0
Tuesday Jan 14, 2014
Monday Dec 03, 2012
By Tori Wieldt-Oracle on Dec 03, 2012
Have you updated to Java SE 7? Along with great features (Fork/Join, NIO, Project Coin), Java SE 7 is being updated and patched regularly. Java SE 7 has been out for over a year and is ready to download.
The last publicly available release of Oracle JDK 6 is to be released in February, 2013. This means that after 19 February 2013, all new security updates, patches and fixes for Java SE 6 and Java SE 5 will only be available through My Oracle Support and will thus require a commercial license with Oracle.
Java SE Support for continued access to critical bug fixes and security fixes as well as general maintenance for JDK 6. Additionally, Java SE Advanced and Suite offers superior diagnostics and manageability tools that minimize the costs of deployment, monitoring and maintenance of Java-based IT environments.
The Java SE Support Roadmap reflects an updated timeline for the End of Public Updates for JDK 6. The End of Public Updates date has been extended from November 2012 to February 2013, to allow some more time for the transition to JDK 7. Older releases of Java SE 6 will still be available on the Java SE archive, but will require a commercial license with Oracle for any new security updates, patches and fixes.
Th End of Public Updates for Java SE 6 will not impact the usage, availability, patching of Java SE 6 used for Fusion Middleware 11g and 12c. The support schedule for Java SE used for and in Fusion Middleware is not impacted by this announcement.
For More Information
Visit the Java SE page on Oracle.com.
Monday Mar 05, 2012
By Tori Wieldt-Oracle on Mar 05, 2012
My favorite biology professor once said "We have to die, if we didn't, the planet would get awfully crowded!" We've just got to put an end to some things so we can focus on the new. It's with that thought in mind that we discuss the End of Life(EOL) of some Java releases. It's always been that Java releases are EOLed after a certain time and users are encouraged to migrate to the latest release. With such a long time between Java 6 and Java 7, maybe people forgot that EOLing happens at all!
The EOL date of Java SE 6 is November 2012. EOL doesn't mean you can't use a Java release. EOL just means the end of public support and fixes, and for that reason, you are encouraged to update to the latest stable release(Java SE 7 has great features and enhancements!). If you need support after the EOL, you can get Java SE Support from Oracle.
In the JavaFX world, JavaFX 1.2 and JavaFX 1.3 have been EOLed. This is end of support for JavaFX script. If you are currently creating JavaFX 1.x applications, you are strongly encouraged to migrate your applications to JavaFX 2. Let's make room for the next generation of Java.
Java SE Support Roadmap
Henrik Stahl's blog Updated Java 6 EOL Date
Donald Smith's blog EOLing a Version of Java is a Process, Not an Event
Friday Aug 12, 2011
By Tori Wieldt-Oracle on Aug 12, 2011
By Henrik Stahl, Sr. Director, Product Management, Java Platform Group
This blog entry will be used to host commonly asked questions related to Java 7. I have pre-seeded it with a few that have come up since the July 28 release. If you have additional questions, feel free to post as a comment to the blog. I will not respond to them in the comments, but will instead aggregate and update the blog entry. Only questions of general interest to the community will be answered here. Fire away!
Q: When will JRockit be available for Java 7?
A: It won't. As we explained last year we are merging JRockit and HotSpot into one single JVM. JDK 7 contains the first release of this converged JVM, where one of the first steps was to start removing the PermGen concept. Future JDK 7 updates will complete the PermGen removal, as well as add more visible features from JRockit.
Q: Where can I find the source code?
Q: Why isn't Java 7 available on java.com yet?
A: The site java.com is used for end-user downloads. As with previous major versions of Java, JDK 7 is first made available to developers so that they can ensure that their Java programs work with the new JRE version before it gets rolled out to millions of end-users.
Q: Where can I find API documentation?
A: Javadocs are available here.
Q: What is the status of the port of Java 7 to the Mac?
A: Feature development is still going on in the OpenJDK Mac OS X Port 7 Project. You can see the detailed status here. Once that Project has made sufficient progress - say a couple of months from now or so - we plan to build and make a developer preview available from the main JDK download site. We will then work with Apple and others in the Mac OS X Port Project to finalize remaining feature work such as installers and plugin/webstart, and then go through the usual steps of one or more beta releases and/or release candidates before we get to GA. If you are anxious to get started, there are a number of third parties that provide binary builds from the OpenJDK code. Just use your favorite search engine and you'll find several.
Q: I have read about issues with Apache Lucene running on JDK 7, what is that about?
A: The Lucene project has reported that running Lucene triggers a JIT bug that causes a JVM crash. It can be worked around by disabling the broken optimizations with command line options, see the bug reports for details. The three bugs that Lucene reported have been fixed in the OpenJDK code, in addition to a fourth bug impacting Lucene that Oracle found (7070134, 7068051, 7044738, 7077439), and are included in current builds of JDK 7 Update 1 (and will remain included unless the fixes cause regressions). For more information on how Oracle prioritizes and works with external bug reports see this blog by Dalibor Topic. And while I'm at it - many thanks to all those of you who have tested JDK 7 and reported issues!
Q: I read the JDK 7 license. It mentions something about Commercial Features, what does that mean?
A: Sun had a habit of creating a new license for every version of Java they released (including every update release). While the modifications were minor, it still meant that you had to call in the lawyers every time to verify that any changes from the previous ones were still acceptable to you. Our goal is to minimize the number of licenses we use, ideally getting it down to only one. When we made JRockit free we modified the Binary Code License to make it cover all versions of Java, as well as JRockit. This was announced in one of my previous blog posts. The "Commercial Features" clause is there to allow us to port over value-add features from JRockit to the converged Hotspot/JRockit JVM starting with JDK 7. Full details on what features are non-free can be found in the product documentation. In the standard JDK 7 GA binaries, there are no commercial features so there is no risk that you use them by mistake. As we move such features to JDK 7 in a future update, our plan is to require an explicit flag to enable them. Note that these features are only restricted "for any commercial or production purpose" so individual developers need not worry. For full information, read the license text itself.
Originally published on Henrik's blog.
Tuesday Aug 09, 2011
By Tori Wieldt-Oracle on Aug 09, 2011
by Dalibor Topic, Java F/OSS Ambassador, Oracle Java Platform Group
The JDK 7 Updates Project in OpenJDK is now up and running. We've spent some time in the past couple of weeks discussing processes, finalized them, and started accepting changes destined for JDK 7 Update releases.
Changes going into a JDK 7 Update are typically bug fixes, coming to JDK 7 Updates through JDK 8. Bugs get reported through several channels - for example through Oracle's QA engineers running tests on early access builds, an OpenJDK developer working on some piece of code, or through the web bug report form.
When a Java developer or end user reports a bug through the web bug report form, a process kicks off. All bugs coming in through the web bug report form start with the initial priority 4, i.e. 'Low'. Priorities can go from 5, i.e. 'Very Low' all the way up to 1, i.e. 'Very High'. When you're starting to hack on OpenJDK, it can be easier to do so by picking out a couple of P4, or P5 bugs from the bug database in order to learn how the processes work with some success before you go on to tackle harder tasks.
There is a WebBugs team at Oracle that reviews the incoming bug reports, in order to weed out duplicates, or misfiled issues, and if necessary request additional information from the submitter. Not all bugs are created equal, so the low priority automatically assigned by the system to the incoming bugs sometimes needs to be adjusted, as well.
When adjusting the priority of a bug, we look at three aspects: Impact, Likelihood & Workaround. Impact is determined by taking a look at how severe an issue is: A VM crash would have a high impact, for example. On the other hand, the likelihood of the crash occurring could be very low. And finally, the existence of a workaround, in particular an easily applicable one, would also impact the priority of the bug. A high impact bug that strikes often and has no workaround would accordingly get a higher priority then a 'benign' bug that occurs rarely and has an easily applicable workaround.
The priority is not set in stone - as OpenJDK developers start investigating an issue in order to produce a fix for JDK 8, new information regarding impact, likelihood or workaround can emerge, resulting in an update of the bug's priority. For example, if a bug turns out to have a much higher likelihood to occur then initially thought, that could be a good reason to raise its priority. On the other hand, if e.g. an easily applicable workaround is found, that could be a good reason to lower it.
Another important dimension of a bug, along with its priority, is its state. For bugs in process of being addressed, there are three important states to be familiar with: 'Fix In Progress', 'Fix Available', and 'Fix Delivered'. The first one (obviously) means that a fix is in progress. 'Fix Available' means that a fix has been delivered into an OpenJDK Mercurial forest. Typically, the bug's evaluation in the bug database is updated to include a URL to the commit in OpenJDK, as well - look for the line starting with "http://hg.openjdk.java.net" if you want to see the source code for a specific bug fix. The fix then progresses through a sequence of integrations into the respective Project's master. For JDK 7 Updates that sequence is fairly short, since we only have one integration forest (jdk7u-dev) in OpenJDK. Finally, once a fix appears in a build, its state is set to 'Fix Delivered'.
With these two bits of information, you can follow along your (and other people's) issues progress in JDK 8 and JDK 7 Updates. For some code, like HotSpot fixes, the path can be a bit longer, since the HotSpot team uses the HotSpot Express model to develop stable versions of HotSpot into multiple JDK releases, so the fix first needs to make it into a HotSpot build, before it can get into JDK 7 Updates through a bulk change. As fixes progress through integration stages, our testing machinery is hammering on them to make sure they work well, work well together, and hold up under pressure.
So, thanks for testing JDK 7, and letting us know about the bugs that bug you. With JDK 7 Updates now up and running, you can help us weed regressions out by testing early access builds, and of course by following along on the jdk7u-dev mailing list as fixes are proposed, reviewed and approved for JDK 7 Updates, and reporting issues you find to our bug tracker.
On a side note, we're working on updating our bug tracking infrastructure used in OpenJDK, which should further increase the transparency of both JDK 8 and JDK 7 Update development in the future.
(originally published on Dalibor Topic's blog.)
Tuesday Aug 02, 2011
By Tori Wieldt-Oracle on Aug 02, 2011
GlassFish 3.1.1 was released last week; congratulations to the GlassFish community! GlassFish 3.1.1 now supports Java SE 7, including the Java language improvements provided by Project Coin, and you can also benefit from the Java SE 7 JVM improvements. Other features include:
- More extensive platform support with AIX 6.1 and 7.1 integration and support for Solaris 11 Express Edition
- Better performance and faster runtime on Oracle GlassFish Server with 64-bit load balancing plug-in support
- Performance and stability enhancements to Weld, EclipseLink, and Jersey runtimes
- New in EclipseLink 2.3: support for multiple tenants, composite persistence units, and extended entities
- Support now available for OSGi/HTTP, OSGi/Web, OSGi/JDBC, OSGi/Java EE Hybrid applications
- Improved fidelity when using GlassFish Embedded APIs
GlassFish 3.1.1 Download
GlassFish 3.1.1 Release Notes (PDF)
GlassFish 3.1.1 Documentation Set
GlassFish Podcast with GlassFish Engineering Manager Sathyan Catari
The Aquarium Blog for GlassFish News
Monday Jul 25, 2011
By Tori Wieldt-Oracle on Jul 25, 2011
Java 7 is scheduled to be made available on July 28th. But first, we have some friends in the community to thank. The Java SE 7 Honor Roll is a list of those great developers who took the Java SE 7 Preview on a test drive and reported bugs. (It is not the complete list, but rather all those who responded to us and provided permission to print their name on the Oracle Technology Network.) Thank you, and your Java 7 T-shirts are on their way!
Alpes JUG Enjoy Their Java 7 T-shirts
(photo courtesy Ludovic Poitou)
Thursday Jul 07, 2011
By Tori Wieldt-Oracle on Jul 07, 2011
The events were held in Redwood Shores, California; São Paulo, Brazil; and London, England and linked together via satellite. In Redwood Shores: Adam Messinger, vice president of development, Fusion Middleware, welcomed everyone and gave a an overview of Java 7. Mark Reinhold explained that the most important thing about Java 7 is that it is finally shipping. ("Java is waking up from its nap" opined the twitterverse).
In London: Ben Evans, author and member of the Java SE/EE Executive Committee, mentioned that the financial sector are looking forward to adopt Java 7 as soon as possible. A representative from the Royal Bank of Scotland explained that RBS relies on the JVM, a TB (Terrabyte!) of in-memory data 24 x 7, and is looking forward to Java 7 improvements. In São Paulo: Bruno Souza, founder and president of SOUJava and member of the Java SE/EE Executive Committee, spoke to developers about Java and its relationship to other languages. One community member was wearing Python jacket over a Java T-shirt, a nice metaphor. Bruno also stressed the importance of the the Java community: "Java User Groups: your participation is fundamental to the future of Java" he said.
Back in Redwood Shores, Trent Gray-Donald, Java Tech Lead for IBM called Java 7 "a great release with strong technology." Bill Blosen of Hewlett Packard said "We are pleased that Java is moving forward and addressing the needs of the Java programming community." Mike Milinkovich, Eclipse Foundation echoed Bruno's sentiment when he said "Rule #1 of Open Source: Show up!"
After the opening session, there were detailed technical presentations on Project Coin, the Fork/Join Framework, the New File System API, and improvements to the JVM. A replay of the webcast and presentations will be available next week.
Today's events was just the start of the celebration. Java User Groups (JUGs) around the world are hosting events from July through September to celebrate Java 7. Oracle has provided JUGs with Java 7 technical presentations, related technology modules, T-shirts for JUG members, and speakers. View the JUG map of Java 7 events.
View the webcast or join a JUG event and see how we're moving Java forward together.
Tuesday Jul 05, 2011
By Tori Wieldt-Oracle on Jul 05, 2011
You know Java 7 is coming, but what exactly is in it? Is Java 7 evolutionary or revolutionary? What are the main features in Java 7? Learn about Project Coin, invokedynamic, and NIO. Join key Java stakeholders Adam Messinger, Mark Reinhold, John Rose and Joe Darcy as they discuss Java 7.
If you want to learn more, join the live webcast on Thursday, which will include these sessions presented by Java experts:
- Making Heads and Tails of Project Coin: Small Language Changes in JDK 7
- Divide and Conquer Parallelism with the Fork/Join Framework
- The New File System API in JDK 7
- A Renaissance VM: One Platform, Many Languages
Thursday Jun 30, 2011
By Tori Wieldt-Oracle on Jun 30, 2011
Do you like the new Duke? Have you gotten the new Duke screensaver yet? Follow @java or Like I <3 Java on Facebook and get the latest 3D, animated "Future Tech Duke" screensaver.
If you haven't already, register now to watch the global July 7 Java 7 community celebration and learn more about Java moving forward. We are looking for questions from the community to be asked during the panel Q & A. Enter your questions as a comment here, or tweet it with #java7.
There's lots of great content being created for Java 7: technical articles, videos, updated web pages (can you say "layer cake?"), T-shirts, presentations, and there will be lots of Java 7 content in the new Java Magazine.
See you at the Java 7 celebration event! Duke will be there!