Posted by editor
on November 6, 2008 at 7:29 AM PST
Does Swing have a future outside of JavaFX? Also:
Forum Posts: Past/present/future of Swing, Eclipse plug-in for GlassFish v3 Prelude, and LWUIT design philosophy
Feature Article: Sending Messages Using JBI Technology
Java Today: WebBeans (JSR-299) public draft, AppFuse moves from Spring XML to annotations, and configuring JSON for RESTful web services in Jersey 1.0
Weblogs: Updating Grizzly version in GlassFish v3 and JSR 286 Implementation and IPC
Does Swing have a future outside of JavaFX?
The quiet storm that's been building since last week's post that Sun is no longer funding the Swing X project comes to a head today, as two of the most prominent voices in Java GUI-dom speak up.
In his blog Sun setting down on the core Swing (cross-posted with a comments section to Pushing Pixels ), Kirill Grouchnikov says that "core Swing is in the process of being retired as a legacy UI technology inside Sun, and last week has marked another sad (yet expected) milestone - stopping the funding of SwingX project."
Kirill cites as a turning point the January 2007 announcement that Sun was dropping SwingX's painter layer. Kirill says "this has effectively destroyed the trust of external contributors, who never came back, even after Sun developers have retired themselves from being involved in the project." Worse, he says, is that the Sun engineers then pulled out of SwingX to focus on JavaFX, with a further impact on Swing:
I don't know what the future holds for JavaFX. Sun is heavily betting on it, and nobody wants to have their Nomad moment forever archived on the Internet. All i know is that JavaFX has effectively halted all core Swing development. Over the last 18 months, we have seen significant architectural initiatives (JSR 295 and JSR 296) changing leads and frozen. All client-facing improvements in Java2D, AWT and Swing in Java 6 Update 10 are completely driven by the requirements of JavaFX.
So, there's one reaction: Kirill, who knows more than a little about working with Swing, sees it being reduced to maintenance mode with no purpose other than to serve as JavaFX's GUI library.
Josh Marinacci, who also gets to claim a spot as a Swing expert says the rush to gloom (the mood, not the Photoshop filter) is premature. In his forum followup , he says that SwingX and SwingLabs continue on, and that Swing developers will benefit from recent changes in Java SE 6 Update 10 and ahead in Java 7.
As a life long client Java developer I have never been happier with
the current state of the Java stack. Client Java applications are
becoming faster, more reliable, and easier to develop. And this is
true for both Swing and JavaFX applications. Stay tuned for the 1.0
release of JavaFX. I think you will be happy when you see what we've
been working on. It's an exciting time to be a GUI app developer on
the Java platform.
For those who want to participate in the ongoing discussion, please note that the discussion has forked into two largely identical threads -- 1 and 2 -- possibly as a result of the recent re-connection of the mailing-list-to-Jive-forums gateway. Apologies for the inconvenience.
Also in today's Forums , Ludovic Champenois promotes a new release in New version of Eclipse plugin for Glassfish v3 Prelude published (v1.0.14) . "Version 1.0.14 of the GlassFish plugin for eclipse was published today. Here is a link to the release notes which lists the bug
fixes that are included: https://ajax.dev.java.net/eclipse/releasenotes.html . Online documentation, tutorial and installation guide is at: https://glassfishplugins.dev.java.net/eclipse34 . Important changes have been done to better support GlassFish v3 prelude, and optimal redeployment of web applications."
Shai Almog explains LWUIT's design philosophy in
Re: Why make so difficult to port J2me component? "MIDP is different from CDC and SE. We tried to create a more unified and sensible layer which allows porting to all platforms (and future platforms) rather than target MIDP developers only."
In our Feature Article , Francesco Azzola offers an interesting introduction to JBI in
Sending Messages Using JBI Technology . "Java Business Integration (JBI) offers a programming model build on assembling a group of components that can be plugged in to a collaborative system. In this article, Francesco Azzola demonstrates basic JBI development and deployment by creating an app that receives requests and sends SMS messages."
In Java Today ,
The Aquarium passes along an announcement that the WebBeans Public Draft is Now Available . "Gavin, the expert lead for the
JSR 299 Expert Group ,
has announced the
First Public Draft of WebBeans
(Download Page ).
You may also want to pencil in November 20th, when
(of Seam in Action fame)
is scheduled to present about
Seam, WebBeans and GlassFish at
TheAquarium Channel ."
AppFuse founder Matt Raible has posted a brief article on Javalobby explaining lessons learned while Moving from Spring's XML to Annotations in AppFuse . "Last night, I did a spike on AppFuse to change XML to Spring annotations (@Repository, @Service and @Autowired) in its service and data modules. While I was able to accomplish everything in a few hours (including converting tests), I did run into a couple issues. "
A new SDN Enterprise Tech Tip from Jakub Podlesak explains Configuring JSON for RESTful Web Services in Jersey 1.0 . "In an earlier Tech Tip,
RESTful Web Services in Java , Paul Sandoz and I introduced RESTful Web Services, JAX-RS, and Jersey, and showed how to
write RESTful web services in Java that conform to the JAX-RS specification.
In this tip you will learn how to configure data in JSON
application returns the information in JSON format."
Finally, Jean-Francois Arcand discusses Updating Grizzly version in GlassFish v3 in today's Weblogs . He writes, "Grizzly releases are always decided by the community and sometimes a bug fixed in Grizzly may takes couple of weeks before it get integrated into GlassFish. If you need to update Grizzly in GlassFish, read on."
Ahmed Hashim wonders about the details of
JSR 286 Implementation and IPC . "JSR286 or Portal 2.0 is the next step in Portal development. It takes long time to get a step in this area; although the commercials solutions like Oracle Portal and Microsoft Sharepoint Portal are far ahead from the standards and open source solutions. The questions is, did any vendor implement JSR286 100% including IPC "Interportlet communication" with JSF & AJAX Integration?"
Current and upcoming Java