Dave Johnson on open web technologies, social software and Java
Crossposted from the Roller project blog
Apache Roller 2.3-incubating is now available via the Apache incubator. For more information about the release see What's New in Roller 2.3 on the Roller wiki. This is a new release, but the Roller 2.3 codebase has been in use for over a month at a number of production sites, including http://blogs.sun.com and this site. Here are direct links to the download files:
Note that we no longer use the wiki for the user and installation guides. Instead, we're using OpenOffice format and generating HTML and PDF versions of these two documents. Here are links to the latest docs for Roller 2.3.
NOTE: Roller is in the Apache Incubator, but this release is not an official release of or endorsed by the Apache Software Foundation. Roller itself is licensed under the Apache license v2.0, but requires some components that have more restrictive licenses (i.e. Hibernate).
Danese Cooper: Earlier this week we all heard about Jonathan Schwartz and Rich Green hinting they were about ready to release Java under some OSI-approved license. Supposedly they just need to nail down "How to Deal with Compatibility". I read this news with some irony, since I know that they bloody well know exactly what to do already. Its been discussed every year since 1999 inside of Sun. Their covenant with Apache and the Geronimo has already successfully demonstrated that it can be done (compatible FOSS reimplementations of Sun-generated specifications). They are simply being disingenuous. What they really mean is "How can we placate the FOSS community without giving up control?" which is the age-old question for Sun.Give us Sun-folk a little credit. If you want open source Java runtimes (and I do), then the announcements this week were most definitely good news. Up until now, we didn't have our story straight. Jonathan Schwartz was telling people that all Sun software would be open source and the OpenSolaris folks were showing us how it could be done, but Java leaders like Gosling (and many others) seemed to be saying that Sun's implementation can never be made open source for fear of incompatible forks. Now we're all on the same wavelength. That is a good thing.
I'm one of the folks responsible for mixing the Kool-Aid. I presented at the W3C Workshop on Web Services (representing Sun). I participated in numerous standardization efforts at W3C, OASIS, WS-I, uddi.org, and JCP. I have a vested interest in making sure that WS-* succeeds.She covers some of the same points I'm covering in my Atom talk (JavaOne 2006 TS-1756), which includes a brief overview of the debate, but she goes a bit further than my slides dare to go with this:
But I can't ignore the debate between REST and WS-*. I'm a huge proponent of the KISS principle. So I don't recommend using WS-* for all service interactions. If an application doesn't require enterprisey infrastructure semantics, then it's much more appropriate to use a simpler middleware system, such as "plain old XML" (POX) over HTTP. In fact, for applications that require Internet scalability (e.g., mass consumer-oriented services), POX is a much better solution than WS-*.Sounds like she mixes the Kool-Aid, but she stopped drinking it some time ago.