Friday Jan 29, 2010

Oracle and Sun Middleware Resources

For my last blog entry here, I thought I'd post a few links for those wondering where they can get more information about Oracle's plans for Sun's middleware offerings.

Oracle hosted a 5 hour event on Wednesday where executives covered all of the plans for Sun's products at a high level.  You can take a look at all of the webcasts and presentations but for Sun's middleware customers, pay close attention to Thomas Kurian's webcast and presentation.

Subsequently, detailed strategy webcasts were made available providing deeper insight into the strategy and plans including timelines for continued support of existing Sun products.  Those of most interest to Sun's middleware customers will be the Application Server, SOA, Identity Management, and Developer Tools webcasts.

As far as my blogging going forward goes, you'll be able to find me at

Friday Jan 08, 2010

Web Apps vs Native Apps: Will we ever fully switch?

When Apple introduced the iPhone, the story was that we didn't need native apps, instead the Web was the application environment and apps should just be written to run in a browser (Mobile Safari).  This didn't last too long as Apple succumbed and the App Store was born and by all accounts, other than developers who can't get their apps approved, it has been a wild success.  I have to wonder though if Steve intentionally made the whole process somewhat onerous to try to encourage folks to still write to the Web as a better and preferred way to get apps to the device.

The success of Apple's App Store has led to other "app stores" or "marketplaces" from mobile phone providers to carriers to the Java Store and more.  So it isn't terribly surprising to see Intel launch a netbook app store, although I have to wonder if the motivation is just to keep up with the Jetsons or if this is the right model for netbooks.  After all, isn't the point of the netbook to leverage Web applications?  If so, is having a store for native apps really needed or desired?  It would seem it is just giving users a crutch to avoid making the transition to the world of applications on the Web.

So why is this?  It is a combination of several things including more developers being comfortable and adept at creating native apps, HTML5 not being ready yet (an excuse for the original iPhone, less of one now), and users being familiar with native apps or fearing not having access if they are out of range of the network so thinking they have to have them.

But there are significant advantages to a world of Web apps.

For developers, while it may never truly be write a single Web app and use it from any device, there is a whole lot more reuse and leverage from creating apps for the Web rather than creating N native variations.  Particularly when platforms like the iPhone refuse to support Java or insist on requiring development in Objective C.  Being able to have an addressable market of multiple mobile and desktop platforms is a huge advantage over targeting one specific platform.

For users, using Web apps allow access to the same app and data from any device without having to perform complex and error prone synchronizations.  Whether you need to access your e-mail, calendar, documents, games, whatever, being able to do so from multiple devices should be a huge benefit if users can just get over the notion that they don't have the app in their possession on their device.

So when will the transition occur?  It will happen first with mobile and lighter weight "netbook" type of devices.  These are (or should be) designed for the Web and will have less storage and general horsepower to run native apps and so are well suited to it.  It perhaps will take something like Chrome OS to do it as other Windows, Linux, or OS X based devices will always have at their core an OS built for native apps.  Chrome OS will change this as far as we can tell.

In the mean time, go ahead and make it a point to ask "could this be a Web app" when creating that next application.  You may be surprised what is possible and how many more devices and users you can reach. 

Wednesday Jan 06, 2010

GlassFish ESB 2.2 Released

We had a busy December releasing Java EE 6 and GlassFish v3, but the good news doesn't have to stop with the beginning of a new year and so it was great to see that our SOA team recently released GlassFish ESB 2.2.

What is new you ask?  There are a host of updates and new features including support for newer versions of GlassFish and NetBeans and support for the latest operating systems, as well as some new components including the E-mail Binding Component (BC), REST BC, and POJO Service Engine (SE), but what is perhaps more interesting is the introduction of a couple of Packs.

The Healthcare Pack extends the functionality and features of GlassFish ESB to healthcare organizations who are focusing on  improving the exchange of electronic health care information.  It includes the HL7 Binding Component, Sun Master Index, and the PIX/PDQ Solution.

The Platinum Pack extends the base ESB with some additional components including the Worklist Manager Service Engine, the Intelligent Event Processor SE, the COBOL Copybook Encoder, the BPEL Monitor, and a new Event Management API.

All in all, some great capabilities have been added to an already outstanding integration platform. 

Interested in more info?  You can download the bits, see more on, visit the community, or attend a training course.


Monday Dec 21, 2009

Java EE 6 and GlassFish v3 Virtual Conference Replays Available

Following up on the release of Java EE 6 and GlassFish v3, we held an online virtual conference last week and I'm pleased to share replays of all of the sessions are now available.  For those that weren't able to attend or missed a session or two, this is a great way to catch up and watch the sessions at your leisure.

The sessions available for replay are:

  • Java EE: The Foundation for Your Business
  • Java EE 6: An Overview
  • GlassFish v3 - Java EE 6 Reference Implementation & Beyond
  • Enterprise Java Beans (EJB) 3.1 Features
  • Jersey, JAX-RS and REST with GlassFish v3
  • Java Servlet 3.0
  • Java Persistence API (JPA) 2.0
  • Java Server Faces (JSF) 2.0
  • Web Services in GlassFish
  • Context Dependency and Injection (JSR 299)
  • OSGi in GlassFish v3
  • Dynamic Languages with GlassFish v3
  • Tools for GlassFish v3: NetBeans and Eclipse
  • Grizzly: NIO & Web Framework. Comet using GlassFish
  • Monitoring, Management in GlassFish v3
  • Java EE Connector Architecture 1.6

I hope some of you take advantage of the opportunity and a little free time over the break to tune in!

Sunday Dec 13, 2009

More Response to the Java EE 6 and GlassFish v3 Launch

See the first round of articles I found gleaning the web on our launch last week of Java EE 6 and GlassFish v3, but here are more:

Thursday Dec 10, 2009

Initial Response to Java EE 6 and GlassFish v3 Launch

As you can imagine, there has been a lot of activity in the blogosphere resulting from our launch today of Java EE 6 and GlassFish v3.  A sampling:

  • Sun Releases Java EE 6, GlassFish v3, and NetBeans 6.8 - A nice DDJ article.  One highlight: "One development feature that I find particularly useful is Session Retention. With this, while debugging a problem in your web or enterprise application, as you make changes NetBeans and Glassfish save your session and application state so that you don't need to restore it each time you restart Glassfish."
  • Sun Ships GlassFish Enterprise Server v3 - eWeek article with a nice quote on a very important point.  "Developers can start with the Web Profile and grow to the entire platform as their needs grow."
  • Java EE 6, GlassFish v3 and NetBeans 6.8 Released - InfoQ story that includes a nice Q&A with Roberto, one of the Java EE 6 spec leads.
  • Sun releases Java EE 6 - Another summary story, this one from SDTimes.
  • GlassFish v3 - The First List of Firsts - A great list of items you may not be aware of.
  • First look at GlassFish v3 performance - Not completely scientific and tuned, but results show v3 is better than v2 (which itself set world record benchmarks in the past), and significantly better than JBoss and Tomcat.  In fact, JBoss and Tomcat failed to complete the scale test even with fewer users than GlassFish was able to support on the same hardware.

Wednesday Dec 09, 2009

GlassFish Enterprise Server v3: The First Java EE 6 Compatible Application Server

Today we released Java EE 6 and the Java EE 6 SDK.  In addition, we've also released GlassFish Enterprise Server v3, the first Java EE 6 compatible application server.

This is the culmination of over 3 years of work by many members of the JCP, community, and engineers at Sun and other companies that have contributed to the specifications and implementations of them, and interestingly comes nearly 10 years to the day since J2EE 1.2 was released in December of 1999.  My thanks go to all involved, particularly the members of my team that made this all possible.

Naturally, one might ask, why is this important?  You can see the Java EE 6 and GlassFish Enterprise Server v3 press releases for more details, but I'll highlight some of the important things here.

Java EE 6 is important for many reasons, not the least of which is that it continues the development, maturation, and innovation of the standard for enterprise Java development.  Past releases of Java EE have continued to add few features and capabilities from servlets, EJBs, and JMS in early releases, to rich Web services support and ease of development features like annotations and EJB 3.0 in Java EE 5 three years ago.  Java EE 6 continues to add new features like RESTful Web services, dependency injection, and annotation additions for Servlets further reducing the amount of code a developer must write, but also aims to provide a more extensible and more flexible platform through the introduction of profiles and pruning.

With the Web Profile, there is now a standard set of components defined as part of the specification that will allow compatible implementations optimized for modern Web applications where the full Java EE stack is not required.  This will result in lighter weight servers requiring fewer resources that start in a fraction of time past Java EE servers have required.

But a fantastic specification is of little use without a commercial product being available that customers can confidently deploy their applications to knowing that it is ready for such use and that has the backing of an organization ready to support it.  This is why GlassFish Enterprise Server v3 is so important, as it is available today, at the same time as the SDK.  And with the introduction of the GlassFish v3 Web Profile, developers and organizations can use a platform optimized for modern Web applications while at the same time knowing they are using a standard and product that will allow them to move up to full Java EE 6 at any time without requiring any changes or re-implementation.

While a straight forward implementation of Java EE 6 would be very valuable given the strides it has made, GlassFish Enterprise Server v3 goes much further in a number of areas.  These include a modular runtime based on OSGi providing for a faster startup and loading of only those components that are required, the ability to run containers for other languages like JRuby and Jython, an Update Center for updating components and adding new components through an easy to use console, and new iterative development features that enable and edit->save->refresh development cycle for Web applications where redeployment is not required and session state information is preserved.

But realizing the benefits of a great server is only enhanced when you have great tooling.  That is why the announcement of the release of NetBeans 6.8 is also very important, as just like GlassFish is providing a full commercial Java EE 6 implementation at the same time as the SDK is released, NetBeans is also providing full support for Java EE 6 with this new release.  For those that prefer Eclipse, there is also a new GlassFish Tools Bundle for Eclipse that has been enhanced to add support for Java EE 6.

I can only write so much in a blog entry, and those that have made it this far are probably interested in learning more, and so I'm also pleased to announce that there will be an on-line virtual conference next Tuesday December 15th.  Please visit the registration page to sign-up and prepare to participate in a number of sessions covering a summary of what is in Java EE 6 and GlassFish v3 as well as detailed sessions on EJB 3.1, JPA 2.0, JSF 2.0, OSGi, and much more.  The spec leads and other developers and experts will be on-line to answer your questions as well.

In summary, visit our Java EE 6, GlassFish v3, and NetBeans 6.8 sites to learn more and download the bits, and register for the conference to take advantage of the information and access that will provide you.  We are confident you will like what you see!

Thursday Dec 03, 2009

links for 2009-12-3: Why JRuby?; NBC and Comcast

Tuesday Dec 01, 2009

Java EE 6 Approved by the JCP

I was pleased to see that JSR-316, better known as Java EE 6, was approved by the JCP Executive Committee today.  You can see the voting results on the JCP web-site.

While I can't say I waited up until midnight to check the voting like Roberto Chinnici, the spec lead for Java EE 6, I was anxiously awaiting the results this morning.  Roberto has a nice write-up on his blog, but suffice it is to say this is a pretty big deal as there are numerous new features and updates in the areas of ease of development, extensibility, and right-sizing including:

  • Servlet 3.0 - Significantly reduces the amount of code/descriptors required
  • JPA 2.0 - Provides flexible modeling capabilities, expanded O/R mapping functionality, and more
  • Web Profile - A subset of the full spec optimized for Web applications

The Web Profile in particular is exciting because it provides a way for vendors to offer smaller footprint, faster starting, and just generally more nimble servers that will allow developers to rapidly build modern Web applications adhering to the Java EE spec allowing them to move up to the full spec whenever needed with virtually no changes.

Stay tuned for more news about Java EE 6 and GlassFish in the next few weeks, but if you are interested in learning more about Java EE 6, take a look at John and Harpreet's recent webinar


Monday Nov 30, 2009

links for 2009-11-30: Old school Microsoft coders; VirtualBox "Teleportation"; Google more closed than Microsoft?

Tuesday Nov 24, 2009

links for 2009-11-24: NoSQL required?; Data Driven Decision Making; Chess Olympiad uses Sun

Monday Nov 23, 2009

links for 2009-11-23: Steve Jobs hates the App Store; ChromeOS

Saturday Nov 21, 2009

links for 2009-11-21: Using EC2 to bypass IT; Why not Affero GPL?; Wolfram Alpha

Monday Nov 16, 2009

links for 2009-11-16: Google and Governments; AT&T on Sun's Cloud; GlassFish and Egyptian Seafood

Friday Nov 06, 2009

links for 2009-11-6: Android explained




« July 2016