Blogging Roller

I just posted the slides for my ApacheCon US 2007 talk on the ApacheCon wiki. It's basically the same talk that I gave at ApacheCon EU earlier this year, but I spent some time tweaking the slides, simplifying removing unnecessary bits and adding a little Abdera coverage. That, and the fact that the power did not fail, seemed to make the talk go more smoothly this morning. Here are the slides:

Apache Roller and blogs as a web development platform (2MB PDF)

• Sound Opinions from Chicago Public Radio and American Public Media
  Best podcast ever


• The Aquarium: GlassFish Interim Governance Board - Now Complete
  "The complete roster is Tony, Greg Luck (Wotif.com) and Pierre Delisle (Google), and Simon and myself (Sun)"
• Bistro!: GlassFish/SJS AS in production - which bundle, which profile, ...?
  Explains differences between developer, cluster and enterprise profiles
• GlassFish Podcast: The GlassFish Podcast
  Finally, a Glassfish podcast! Props to Alexis Moussine-Pouchkine
• Apple - Downloads - UNIX & Open Source - GlassFish
  Download Glassfish V2 directly from Apple
• Red Hat and Sun Collaborate to Advance Open Source Java Technology
  "Red Hat has signed Sun's broad contributor agreement that covers participation in all Sun-led open source projects."


• Megginson: First looks at OpenSocial: part 1 (URLs)
  Lists the URIs for the AtomPub collections available in OpenSocial
• Megginson: First looks at OpenSocial: part 2 (members and friends)
  How OpenSocial members and friends are represented in Atom format
• Megginson: First looks at OpenSocial: part 3 (activities)
  How OpenSocial activities are represented in Atom format and manipulated via AtomPub protocol
• Megginson: First looks at OpenSocial: part 4 (persistence data)
  How OpenSocial persistence is implemented via AtomPub protocol
• Google: OpenSocial Container Sample
  Shows "basic demonstration-level OpenSocial container can be implemented"
• Dare Obasanjo: OpenSocial Tech. Overview and Critique
  "Despite these misgivings, I think this is a step in the right direction. Web widget and social graph APIs need to be standardized across the Web."


• snellspace.com: Notes, Part 2
  "lots and lots of things that can be modeled as collections of web resources"
• netzooid: Building Services with AtomPub
  "While APP is not the one true protocol, I think I?m hooked"

The next releases that I'd like to announce are the Blogapps 2.1 Examples and the Blogapps 2.1 Server.

If you'd like to learn more about the Blogapps examples and server then read The Blogapps Project article at Java.net. Here's a quick summary:

The Blogapps project hosts a collection of useful RSS and Atom utilities and examples from RSS and Atom In Action by Dave Johnson. They're designed to be useful even if you haven't read the book and they're available under the Apache License 2.0 so you can use the code in your applications and you can modify and redistribute them as you wish.

What's changed since 2.0? The examples have been updated to include the latest version of ROME Propono, which means that most of them now support the final Atom protcol spec. The server has been updated to include Roller 4.0 RC5, which also includes Atom protocol support and JSPWiki 2.4. And of course, various bugs have been fixed. Here are the release files, installation instructions and release notes.

• Blogapps server install instructions
• Blogapps Server-2.1.tar.gz
• Blogapps-Server-2.1.zip

• Blopapps example release notes
• Blogapps-Examples-2.1.tar.gz
• Blogapps Examples-2.1.zip

This blog entry was posted via Atom protocol and the MatisseBlogger blog-client, which you can see in the screen-shot below (which was also posted via Atom.

What's next? Not sure at this point, but I will do another Blogapps release once ROME 1.0 is released.

The first release to discuss is ROME Propono, which includes a ROME based Atom protocol client library, Atom protocol server framework and an Blog Client library abstraction that supports both Atom protocol and the MetaWeblog API.

I've been working on Propono 0.6 off-and-on since May, keeping it in sync with the latest version of the Atom protocol, testing it against Tim Bray's APE and adding various improvements needed in my other projects. Over the weekend I finally had enough time to get a release out. You can find the full-details at the link below but basically this release adds support for the final Atom Publishing Protocol specification and better support for relative URIs.

• ROME Propono 0.6 release notes / change list
• API documentation
• Propono 0.6 Binary tar.gz
• Propono 0.6 Binary zip
• Propono 0.6 Source tar.gz
• Propono 0.6 Source zip

What's next? Once ROME 1.0 is released Real Soon Now, I'll get a another release out and I'll probably call it ROME Propono 1.0.

Congrats are also in order for the JSPWiki team. As Janne Jalkanen notes, JSPWiki was accepted into the Apache Incubator yesterday. I'm proud to be one of the four mentors who will guide the project through the incubation process. Janne and the JSPWiki team put together a great proposal and I think it was clear to everybody involved in the vote that these folks know what they're doing. They'll master the Apache way in no time.

Yes this is my obligatory Glassfish V2 post but listen, for me V2 is a pretty big big deal. Like Eclipse, which was the IDE that pulled me away from VIM, Glassfish V2 is the app server that finally pulled me away from Tomcat.

You see, I've been using Tomcat every day for a very long time. I started back in 2000 when I worked at HAHT Software and I was working on the new "Rocketsled" J2EE version of the HAHTsite app server. We were ripping out the old proprietary page engine and plugging in Tomcat. It was a pleasure to work with and I learned a hell of a lot from the code-base. After joining Sun and switching from Eclipse to Netbeans because Sun-on-Sun matters, I still stuck with Tomcat. It's what we were using for blogs.sun.com and Glassfish was just too bulky and slow. I grew to love Netbeans, but I couldn't stomach Glassfish, until now.

Now that Glassfish V2 is out I'm switching from Tomcat to Glassfish for all of my development. It's more than fast enough. With Glassfish on my MacBook Pro, Roller restart time is about 8 seconds compared to 16 with Tomcat. And the quality is high; the admin console, the asadmin command-line utility and the docs are all excellent. The dog food is surprisingly tasty ;-)

Congrats to the Glassfish team!

ApacheCon is coming up fast. I just faxed in my speaker's agreement and I'm starting to update my talk to cover the latest changes in the upcoming Apache Roller 4.0 and 4.1 releases.

I've been four times now and ApacheCon is always a great conference. It's small and cozy enough, but almost all of the Apache projects are represented. So it's easy to find the experts, make new friends and get all of your questions answered. The session line-up looks great this year; here are ones that caught my eye:

• Hacking Atom with Apache Abdera - Garret Rooney
• A little REST and Relaxation - Roy Fielding
• WS-* vs. REST: Facts, Myths and Lies - Sanjiva Weerawarana
• Go Light with Apache Struts 2 and REST - Don Brown
• How to Run a Business Around The ASF - Sanjiva Weerawarana
• Open Source Community Anti-Patterns - Ted Leung
• RIAs using Apache Derby and Comet - Jeanfrancois Arcand & Francois Orsini
• Apache Derby - Saucer Separation - Rick Hillegas
• JCR in Action - Content-based Applications with Apache Jackrabbit - Carsten Ziegeler

Want to go? There's still time to shave a couple of hundred dollars off the conference fees by registering early. Early bird pricing has been extended to Sept. 22, 2007.

And the Weston looks like a pretty nice place for a conference:

Todays news that Sun's stock ticker will change from SUNW to JAVA was met with pretty mixed reactions both inside and outside of Sun. On the day of the announcement, the more than 170 comments on Jonathan Schwartz's blog announcement were mostly negative and though there are some positive reactions in the interblogonet, they come mostly from Sun employees.

Below are the posts that I've seen in my feed reader so far.

• Barton George (Sun): "bold move"
• David Van Couvering (Sun): "Wow. Bold, audacious, wild."
• BlogBridge blog: "That’s good news for us" - reaction from a Java ISV
• Nick Wooler (Sun): "reinforces the brand"
• Jonathan Hawkins (Sun): "good idea"
• Bruce Hill (Sun): "certainly a cooler name"
• Glynn Foster (Sun): "massively supportive"
• Jason Beloro (Sun) "already a success"
• Fake Schwartz: "we're open sourcing the stock as well!"
• Marc Kossa (Sun): "I like it !"
• Alexis Moussine-Pouchkine (Sun): "turning out to be a very good communication strategy"

• Evil Geir (ASF): "brilliant" (with extreme sarcasm)
• Geoff Arnold (formerly Sun): "This is simply silly"
• Sam Ruby (ASF): JCP (JCP with the C for Community crossed out)
• Shawn Ferry (Sun): "I preferred SUNW" via Twitter
• Dan Latcher (Sun): "don't see the point"
• Murphee's Rant: "Run for the hills, folks! "
• Dion Almer: "Oh momma"
• Paul Krill, InfoWorld: "likely to cause confusion"
• C. G. Walters: "army of hamsters" (sorry, that's my favorite part)
• Sanjiva Weerawarana (ASF): "incredibly bad idea"
• James Robertson: "dilutes Sun's brand"
• Daring Fireball: "shuffling the deck chairs on the Titanic"
• Catherine Helzerman: "Java isn’t just Sun"
• Tim Bray (Sun): "I hate it."

• James Gosling (Sun): "totally bizarre"
• James Duncan Davidson: "something not to be done lightly" (good story, don't miss it)
• Kevin Chu (Sun): "In light of our change..."
• Jim Jagielski : "The next several months will be very telling indeed."
• Garbage Collection blog (Sun): "Maybe it might work"
• Madhan Kumar Balasubramanian (Sun): "What is this?"
• C. Enrique Ortiz: "[Sun] is very committed to Java"

What do I think? I'm not sure what I think of the change. The ticker SUNW was out of date because "workstations" are so 80s man, so it's a good thing to update it. And Java ISVs like BlogBridge should like the vote of confidence in Java. On the negative side, it's easy to search for SUNW to get Sun news and that won't work as well with the new ticker. And Java's not all Sun does. One more point. I'm not sure most folks really care what the ticker name is. If they did, don't you think Sun would have changed it years ago?

By the way. I didn't mean the hit the post button on this entry so soon, but it's out there now so I might as well let it stand. I'll update over the next day or two as reactions roll in.

UPDATE: Ed Burnette has a positive, neutral, negative and funny breakdown of his 25 favorite comments from Jonathan's blog post. He says that "Stockholders and employees are among the most vocal critics." of the change.

Apache JSPWiki Manifesto: This idea has been brought up before, but so far it has not really been an issue. However, this looks like the time when it would be possible to accomplish this.

JSPWiki code base is old, and it needs some refactoring. This refactoring includes things like moving to Java 5, fixing the metadata engine, replacing the backend with something scalable, and in general removing all the cruft that has been accumulated over time. This requires that we break compatibility with existing plugins and other components. Not badly, but to some degree.

Also, JSPWiki as an open source software project is growing slowly but steadily. However, the wiki world is moving rapidly, and wikis have been adopted widely. JSPWiki has become a tool for a great many companies, who are relying on it in their daily business. This is a lot for a hobby project lead by a "benevolent dictator" -model. Therefore, it is time for JSPWiki to mature to a "real" open source software project to be a serious contender in the wiki world.

To accomplish both of these goals needs a major shift in how JSPWiki is managed and who "owns" it, in a sense. Therefore, we (the people who have been committing source code) think that Apache would be a good choice, and have decided that we will try to submit JSPWiki into the Apache incubation process, with the goal of graduating as a top-level project.

I've been a JSPWiki (and Janne Jalkanen) fan for years now. It's my favorite Java-based wiki so I'm pretty excited that the dev team is preparing a proposal to move the project to Apache. I think this will be a great move and will ensure that the project continues to grow and continues to be a strong contender in the enterprise wiki space. I'm more than willing to help with that proposal and to help out in the Incubator.

I wasn't paying attention and this one snuck-up on me. Today at noon Pacific Time there will be an online Atom Publishing Protocol interop event. The location is IRC on the Freenode network in the #atom channel: irc://irc.freenode.net/atom.

I'm really glad I didn't miss this announcement because I spent much of the last two weekends updating the ROME Propono and Apache Roller 4.0 implementations to work with the final version of APP (draft #17). I've got both implementations online now and ready for interop.

And in kinda sorta related news, one of the founders of the Atom effort Joe Gregorio is leaving IBM and heading over to Google. Congratulations Joe! I hope this doesn't mean you'll be leaving the Triangle behind.

I've been waiting years for this one. As Roumen Strobl points out, the Netbeans 6.0 nightly builds finally include a "go to file" feature, much like CTRL-SHIFT-R in Eclipse (but in Netbeans 6.0 it's CTRL-SHIFT-O).

I'm diggin' 6.0 and it's starting to look pretty stable in advance of beta1, which is coming out this month. Grab a nightly build and check it out. According to Tor on the Java Posse the nightly builds are likely to be more stable than the most recent M10 milestone release.

Good news today from Tim Bray: Atom protocol has been finalized. The final version of the spec is going to be Atom protocol draft #17.

Instead of staying up until the dawn hours (not naming names) reading the final Harry Potter book, I spent most of the weekend working on bringing Propono in-line with the draft #17 and in particular adding support for out-of-line categories and relative URIs. I've got code ready to commit that passes Tim's Ape tests, so hopefully we'll have a new Propono 0.6 release ready very soon that supports the final spec.

Roller's Atom protocol implementation is already up to date and passing Ape tests, so Roller 4.0 will be Atom protocol ready. I still need to do a little work to document the setup.

Project Zero introduces a simple environment for creating, assembling and executing applications based on popular Web technologies. The Project Zero environment includes a scripting runtime for Groovy and PHP with application programming interfaces optimized for producing REST-style services, integration mash-ups and rich Web interfaces.

"This community is an experiment in a new way to build commercial software, an approach we are currently calling Community-Driven Commercial Development. Community-Driven means that we want feedback, insight, suggestions, criticism, and dialogue with you, the users of Project Zero. This interaction will yield a better solution that is more targeted at the problems you have and a technology that truly delivers on its objectives. Commercial means that this is not an open source project."

I stayed up a little too late last night upgrading this site (rollerweblogger.org) to the latest Roller 4.0 code base, which includes the new Struts2 based Admin UI and a new OpenJPA based back-end. No more Hibernate for me. The upgrade was a bit of a rocky road, but the site seems to be working OK now.

© Oliver Mallich

First, an announcement from Covalent. They've rescheduled their Apache Roller webinar with Matt Raible to June 20.

A couple of new users showed up on the Roller mailing-list this week. One was Ryan Delaplante who wrote about his Roller installation experience and the nice new theme he developed on his blog ryandelaplante.com. Jason Johnson stopped by to tell us about the new Roller-based blogging system at the University of South Dakota blogs.usd.edu. They've got some looking themes there too, check out Astra blue and red.

In the blogs, here's a post for Sun bloggers only from Rich Sharples: OpenID Delegation with Roller (take 2). Rich explains how to setup your Roller-based blog as a proxy for your Sun OpenID account.

In development, we're still finishing up the Roller 4.0 release. Most commits this week are coming from Allen who is working on bug fixes across the board. I've been making slow and steady progress on the Roller easy install work. Also, if you look at the Subversion logs you'll see that I'm working in a separate branch to implement Dependency Injection (DI) in Roller via Google's Guice. I'm almost ready to show-and-tell with a proposal. Denis Balazuc has also created a DI implementation using Spring, so we may have some interesting discussions next week.

No significant news about releases this week. We've probably got enough fixes to justify a Roller 3.1.1 release, but nobody has prepared a release candidate yet. I might be able to do one next week.

That's it for this edition. Have a great weekend.

Roller Strong Disclaimer: this is a personal blog and I do not speak on behalf of Sun Microsystems or the Apache Software Foundation. 

Congrats to the OpenJPA team.

Patrick Linksey: Last week, OpenJPA graduated from the Apache incubator, meaning that it's now a fully-fledged Apache project. We're graduating to a top-level project, so once the infrastructure administrivia gets worked out, the new URL will be http://openjpa.apache.org.

I'd like to thank Craig Russell for pushing the project through the last mile of graduation details, and our incubation mentors (Brian McAllister, Eddie O'Neil, and Geir Magnusson) for all their help transitioning into the Apache world.

I'm pushing to replace Hibernate with JPA in Roller and OpenJPA seems the most likely candidate, so I'm glad to hear the community is thriving.

Speaking of open source projects that need help, there's Coyote, which promised to bring scripting support to Netbeans and did so for Netbeans 5.0. Since then, the project has been pretty stagnant. JRuby's getting all the attention these days.

Geertjan is doing his best to jump-start Groovy support in Netbeans, but it's not really his job. He's gone beyond the call of duty and it looks like he's got something pretty functional going, which is very nice. I've been doing some Groovy scripting lately, so I'll try it out. It would be cool if the Groovy project itself had time to help out, or even take over, but they're probably pretty busy too.