Keukenhof #2
Today we took the train from Amsterdam to Leiden and the bus to Keukenhof. I took about 50 photos of the tulips and other flowers there. Here's one of my favorites.
Off to Amsterdam...
Propono 0.5 released
Blogapps 2.0 released
Roller graduation and 3.1 announcement
Finally! Roller has graduated to become a top-level Apache project and we've shipped the long awaited Apache Roller 3.1 release. You can find the full announcement on the Roller mailing list and on the Roller project blog and our new top-level site at http://roller.apache.org.
APP interop follow-up
Following up on the APP interop event last week, here are the ROME Propono APP client issues we found:
- ROME #66 BUG - don't expect entry to be returned from update (FIXED)
- ROME #67 BUG - handle relative URIs in Service Doc
- ROME #68 BUG - handle out-of-line categories in Service Doc
-
ROME #69 RFE - use pluggable auth. scheme w/Google and WSSE support
And here are the Roller APP server issues:
- ROL-1393 BUG - attributes in service doc should not be namespaced (FIXED)
- ROL-1394 BUG - wrong content-type for service doc (FIXED)
- ROL-1395 BUG - support slugs for entries too
- ROL-1396 RFE - RSD support, auto-discovery for APP
- ROL-1397 BUG - null byte 0x0 getting into entry contents
I plan on fixing the Roller issues for this summer's Roller 4.0 release. I won't have time to fix the Propono issues for the upcoming Propono 0.5 release (due this week), so they'll be in 0.6 sometime after JavaOne.
WSO2 Web Services Mashup Server
APP interop event day #2
The Atom Publishing Protocol interop event is over and now I'm catching up on blogs and email in my hotel room in Mountain View, CA. In the end, I was able to run ROME Propono successfully against Blogger/GData, AOL Journals and Wordpress. I also found a dozen small problems in Propono and in the Roller APP server.
For more information on the event, check O'Reilly's Keith Fahlgren's summary of the event titled Atom Publishing Protocol a Success. Keith mentions that "big industry players like AOL, Google, IBM, Microsoft, Oracle, and Sun are working on APP clients and servers and sent people to the interop event with interesting code" and I agree that's definitely a good sign for the protocol.
I thought it was particularly interesting that database vendors IBM and Oracle showed up with DB2 and Oracle-backed Atom stores. If Google's half-dozen or so Atom protocol based services aren't enough make you stand up and take notice, surely that should get your attention.
APP interop event day #1
Day one of the Atom Publishing Protocol (APP) interop event was a success, at least from my point-of-view. I was able to test the Propono client against Blogger.com/GData, AOL Journals and an implementation from Oracle. I found and fixed problems in Roller's APP implementation. Plus, it was great to meet all of the good folks implementing Atom and to get a close look at the Google campus. I'm getting ready to drive back to Google now so... gotta go.
Check out Tim Bray's blog for some photos of the event.
5th anniversary of Blogging Roller
Today is the fifth anniversary of this blog, which I started on April 11, 2002 to promote the Roller blog software that I had just finished writing.
Roller wasn't really ready for deployment at the time, so I started blogging using Userland Radio radio.weblogs.com. You can find my first post on Radio here FIRST POST!!! You can also find the original Roller 0.90 user guide on the old site, complete with screen-shots. A couple of weeks later, my article on Roller was published at OnJava.com and folks started to take notice of Roller.
Now, five years later, Roller has graduated from the Apache Incubator to become Apache Roller, blog-tech is my full-time job at Sun and I'm still Blogging Roller. Thanks to Roller users and contributors everywhere for helping to make this possible.
ROME Propono 0.4 released
I'm happy to announce the first release of the ROME subproject Propono. Propono is a ROME-based Java class library that supports publishing protocols, specifically the Atom Publishing Protocol and the legacy MetaWeblog API. Propono includes an Atom client library, an Atom server framework and a Blog client that supports both Atom protocol and the MetaWeblog API.
Here's the project page
http://wiki.java.net/bin/view/Javawsxml/RomePropono
Here's the Propono 0.4 release page:
http://wiki.java.net/bin/view/Javawsxml/RomeProponoRelease04
And here's a link to the API docs, which include details, diagrams and code examples:
https://rome.dev.java.net/apidocs/subprojects/propono/0.4/overview-summary.html
I'll be testing Propono this week and next (at the Google-hosted APP interop meeting) so now is a great time to provide feedback and bug reports. I plan on releasing Propono 0.5 in the *very* near future.
The O'Reilly Code
Most of Tim O'Reilly's proposed blogger's code of ethics is common sense stuff, but some of it seems to conflict with the informal, conversational and public nature of blogs. It's flawed and besides that, it's unnecessary.
It's not always important to "connect privately before we respond publicly" to "misrepresentations or conflicts" as the code states. Blogging is supposed to be a public conversation, not a bunch of back-channel emails and phone calls. If you think somebody misspoke you might want to check with them before you totally lay into them, but you can do that gently on your blog e.g. "I was reading Bob's post and wondering if he really meant to say 'all foo is bar' because that just doesn't seem right."
It's not necessary for every blogger to take action "when we believe someone is unfairly attacking another;" especially if others are already responding well and being heard. It's OK to lurk.
And I definitely do not believe that anonymous comments should be banned. So I'm glad to see that O'Reilly now says (in the comments to his own post) that part should be optional.
For me the bottom line is that bloggers should follow the same rules as everybody else. We don't need special blogger's code of ethics, a sheriff badge or the blog police. The fundamental things apply: common sense, decency and the laws of the land.
Testing 1 2 3
planet.sun.com
We haven't released the standalone Roller-Planet application yet, but the .Sun Engineering team quietly deployed the latest bits at planet.sun.com a couple of weeks ago in response to requests from the Glassfish, SWDP and other teams for planet-style web sites. You can follow the links on the main page to find planets for Glassfish, SWDP, Sun India, Sun Alumni, Sun Java System Web Server, web services and globalization bloggers.
What's Roller-Planet? It's a community aggregation server, similar to Planet-Planet but with some key differences: it's got a web UI that enables groups of users to run their own planet sites, it's based on Java and it uses the ROME feed parser and fetcher. I've written about it before. We don't have a release plan yet for Roller-Planet so if you really want to try it you'll have to fetch and build it from the Apache Roller SVN repo.
Atom protocol interop event
Atom protocol as the substrate for reliable messaging
I've heard the argument before that the REST approach to web services doesn't give you reliable messaging and that's the reason you need to stick with WS-*. Today Bill de hÃra disputes that notion with an interesting and somewhat provocative post that mentions a couple of specs for messaging via HTTP (HTTPLR and BTF) and argues that Atom protocol can serve as the basis for web-scale reliable messaging.
Bill de hÃra: There are a number of reasons to choose Atom Protocol as the substrate for web-scale reliable messaging. First, a ton of software will be written to target APP in the next few years, and there is plenty of scope for extending the protocol; this suggests openly available and flexible software stacks. Second, since all document collections in Atom Protocol are served as Atom Feeds, it has inherent support for systems management and end to end reconciliation. Third, Atom entries have identity and are natural envelopes, unlike SOAP, where identity and true enveloping requires further specification (essentially raw Atom presents a better basis for interoperation than raw SOAP). Fourth, Atom Protocol can support binary content transmission not just XML, and thus can transmit arbitrary payloads. Finally, because Atom Protocol respects media types and deployed HTTP infrastructure, independent proxy inspection and security check-pointing can be installed cleanly, also eliminating the need to rewrite 2 stack layers and buy XML appliances to support and secure SOAP backed web services. It seems to be a question of when, rather than if, this will get built out.
I would have blogged about this earlier today, but Bill's blog looked foobar and I didn't realize that today is CSS Naked Day. My blog doesn't look half bad naked.
@JavaOne: Beyond Blogging: Feeds in Action
Geertjan's blog
I've really been enjoying Geertjan's blog recently. Lots of interesting details, screenshots and his passion for his work really comes through. His posts on the Netbeans Schliemann generic languages framework and today's Capturing Matisse make me want to drop everything and start hacking Netbeans. And I'm especially happy to see that somebody is interesting in Breathing Life Back into a Dead Coyote (part 1 and part 2), which is currently the main vehicle for Groovy language support in Netbeans -- I'd hate to see Groovy dropped in the mad rush to Ruby.
Happy 10th birthday to Scripting News
« Previous page | Main | Next page »