InfoQ

News

JavaOne 2008 Day 1 - JavaFX, OSGi, and Android Smoke and Mirrors

Posted by Scott Delap on May 07, 2008 09:27 AM

Community
Java
Topics
Leadership
Tags
OSGi,
JavaFX Script,
Java One,
JavaOne 2008
JavaOne kicked off Tuesday in San Francisco with a keynote largely centered on JavaFX. From the press release the roll out schedule for JavaFX is shaping up as follows:
  • July - JavaFX Desktop SDK Early Access
  • Fall - JavaFX Desktop 1.0
  • Spring 2009 - JavaFX Mobile and JavaFX TV

The keynote also featured demos related HD video which Sun's Bob Brewin announced later in the day will be provided be licensing the On2 codec. Perhaps the most interesting demo was a JavaFX application running on an Android emulator. Android does not support JavaME and Sun has not announced support for Android. Later that morning Sun released a statement clarifying the application demonstration:

...during Rich Green's JavaOne keynote, Sun showed a demo of JavaFX running on the Android emulator that was created by the community. The purpose of this demo was to show the portability of JavaFX to other platforms. This is not a product announcement and Sun has no plans around Android at this time...

OSGi also made an appearance ... albeit in a stealth manner with the keynote disclosure of the new Glassfish micro-kernel being 98k in size. As previously announced the HK2 kernel seems to be have been replaced with OSGi. In a likely related move bloggers are reporting that the "Java 7 Module System (JSR-277) will support both - its own format IAM - as well as OSGi".

5 comments

Reply

snooze.... by Tom Nichols Posted May 7, 2008 2:02 PM
Re: snooze.... by Ian Skerrett Posted May 7, 2008 7:01 PM
Re: snooze.... by Ben Loud Posted May 8, 2008 12:50 AM
Re: snooze.... by Tom Nichols Posted May 8, 2008 2:32 PM
Re: snooze.... by Michael Neale Posted May 8, 2008 5:49 PM
  1. Back to top

    snooze....

    May 7, 2008 2:02 PM by Tom Nichols

    So... Has anything actually innovative or newsworthy actually come out of JavaOne yet? Not to fault the writer, I think he's doing the best he can with what he's got. Come on... When the iPhone SDK was announced, a beta was available that day. JavaFX is still vaporware, and I have yet to read anything else interesting from that conference. Jeez.

  2. Back to top

    Re: snooze....

    May 7, 2008 7:01 PM by Ian Skerrett

    I am attending JavaOne and haven't seen anything interesting. It is pretty sleepy for new announcements. The big announcement was last week by SpringSource. Ian

  3. Back to top

    Re: snooze....

    May 8, 2008 12:50 AM by Ben Loud

    Give em a break. Do you think the iPhone was developed overnight? No, developing technology takes time. The difference is other companies keep what they're working on a secret and then make the "big suprise announcement" with a product thats nearly ready to ship. That's great for press releases, but Sun is taking a different approach. They announced their plans early, when they had just begun to develop it, so that they can engage the community as early as possible, develop interest, and encourage the community to help influence it's development through open source projects and feedback. So it's not fair to have a go at them for not having a beta ready yet.

  4. Back to top

    Re: snooze....

    May 8, 2008 2:32 PM by Tom Nichols

    While I agree that a big innovative product doesn't happen overnight, the reason they announced early was that they are playing catch-up. Flex (and Silverlight, to a large extent) are already mature technologies. If Sun had released JavaFX last year they would still have been playing catch-up, save for the community that would have instantly jumped on the technology.

    So here we are, a year later, and still nothing concrete. Now Sun is really behind. I'm not saying it's not a good idea... I mean I'll be glad to have it if/when they finally release it... But the longer they take, the more mindshare they lose to other platforms that are at the head of innovation.

  5. Back to top

    Re: snooze....

    May 8, 2008 5:49 PM by Michael Neale

    "Flex (and Silverlight, to a large extent) " No - NOT silverlight to any reasonable extent. Not at all. Certainly not compared to flex.

Exclusive Content

Tapestry for Nonbelievers

A new article by I. Drobiazko and R. Zubairov introduces v. 5 of the Apache Tapestry component-oriented web framework. The tutorial shows how to create a component and covers IoC in Tapestry and Ajax.

Pete Lacey on REST and Web Services

In this interview, Burton Group consultant Pete Lacey talks to Stefan Tilkov about his disillusionment with SOAP, his opinion on REST, and addresses some of the perceived shortcomings REST vs. WS-*.

Business Natural Languages Development in Ruby

Jay Fields presents his concept of Business Natural Languages - a type of Domain Specific Languages geared towards being readable by domain experts.

Distributed Version Control Systems: A Not-So-Quick Guide Through

Adoption and interest for Distributed Version Control Systems is constantly rising. We will introduce the concept of DVCS and have a look at 3 actors in the area: git, Mercurial and Bazaar.

Segundo Velasquez and Agile as Seen Through the Customer's Eyes

Deborah Hartmann interviewed Segundo Velasquez about his experience as customer with an Agile team during the initial phase of software design of a product.

Fine Grained Versioning with ClickOnce

David Cooksey shows how to fine grained versioning to a ClickOnce deployment using an HttpHandler written with ASP.NET, making partial rollouts to a test audience much easier.

Implementing Manual Activities in Windows Workflow

Windows workflow (WF) is an excellent framework for implementing business processes, but lacks support for human activities. This article describes a completely generic approach for changing this.

Markus Voelter about Software Architecture Documentation

In this interview taken during OOPSLA 2007, Markus Voelter talks about the importance of documenting the software architecture, and gives some good and also bad examples on how it could be done.