Skip to main content

JWSDP components, GlassFish and CDDL

Posted by pelegri on June 27, 2005 at 12:35 AM PDT

We (Sun bloggers) thought there would be no news reports on Sun open sourcing the AppServer until the beginning of
JavaOne tomorrow morning but it seems the news
are out there (see [1] for example).
I don't know if this was intentional or not - some of the
initial pieces came from NZ, so maybe somebody didn't indicate what TZ the release
date was? - but, in any case, we checked (blogging by employees does require some basic coordination to maintain trust across all parties) and we got the go-ahead to talk about it tonight. So...

I will let Jim, Carla, Amy and others talk about some of the other
Here I just want to clarify how this will affect the JWSDP projects.

The decision to Open Source the code base for Sun's App Server Platform Edition includes all
the projects in the JWSDP community that go into that artifact.
That includes

  • JAXP and SJSXP (StAX)
  • JAX-RPC 1.1, JAX-WS 2.0 and JAX-WSA
  • JAXB 1.0 and JAXB 2.0
  • WS Security

Eventually we want all these projects with a live code repository at Java.Net under the CDDL license and with an active developer (including
commiters) and user community.
Some of the above projects are already there,
all will get there as soon as practical.

This is very exciting news to many of us, who have been involved in this
discussion thread for ... hum... do I really want to dwell on that?... let's say
quite a while...
So, yes, this code base is now open source. Now, let's use OSS to
build a stronger community so we can make these implementations
the best implementations available. And so they, together with
other implementations, will make the underlying specifications top quality.

It's going to be interesting to see how the community reacts to this announcement
tomorrow at JavaOne. One thing that sometimes people forget is that
Sun's Application Server (formally known as Sun Java System Application Server, but that is always a mouthfull) is the core of the J2EE SDK, which is downloaded
in very large numbers (see
You should know about the J2EE SDK),
and this move will just make that artifact more useful to the developer community,
and even more popular.



Related Topics >>