Posted by: James Denman
Java FX, Java One
So JavaOne 2013 has come and gone. SearchSoftwareQuality.com staff have been busy at work pitching in with our sister sites to bring out some meaningful coverage of JavaOne and Oracle Open World. JavaOne is the event of the year for Java developers. Oracle Open World runs alongside JavaOne ever since Oracle bought Sun Microsystems and the JCP a few years ago. This year’s big Java news centered around a few big breaks for Java EE 7 and the new features coming soon with Java 8.
There was also considerable talk at JavaOne about continuous integration (CI) and user interface tools. What do these two topics have in common? They were both reported on by the talented Jan Stafford. Stafford dug into the Hudson CI server changes that the Eclipse Foundation announced just before Oracle Open World. Stafford’s source at Oracle expects the team-focused features of Hudson 3.1.0 to make the transition from Hudson 2-3 a short one for many organizations.
Stafford then turned around and covered the client side of things with Java FX. According to Rob Terpilowski — senior software architect at Lynden Inc. — JavaFX has become a more attractive option than Swing for user interface development. Check out this quick Q&A article to find out how and why the team at linden switched from Swing to JavaFX.
No IT conference today could leave out a talk or two about cloud topics. SearchCloudApplications.com senior editor Anne Stuart cut straight to the point with Depu Panda who presented a state of the union address for Java cloud platforms. Panda told Stuart there are plenty of benefits in switching to PaaS tools for development and deployment, but also a few challenges to watch for. Challenges include standards issues, privacy and security concerns, and a cloudy view of the available options. Still, building Java apps on a PaaS can decrease costs and increase flexibility if done right.
Of course I was also fortunate enough to be able to contribute. I got an interview with Java Champion Adam Bien. Bien explained that stress testing is highly underrated. He said stress tests are necessary to ensure that applications are not destroyed by heavy load once they’re deployed. He also said the stress testing processes itself is fun because the only way to find out how much it can take is to push the application until it breaks. Hopefully that means applying way more pressure than your applications are actually going to experience.
That’s the news from JavaOne 2013. Check in soon for coverage of the upcoming STP Conference in Phoenix. And until next time, remember that the only thing worse than heading in to work on a Monday is having no job on Thursday.