Dave Johnson on open web technologies, social software and Java
Linda's written up a summary of her smaller-is-better web application release philosophy and Roller fans take note, one of the projects she manages is blogs.sun.com. That's right folks, we're rolling out new blogs.sun.com releases on a monthly basis. Coming from a software product background, monthly releases seemed crazy to me, but Linda (and Will) have beaten me in to submission.
So, monthly releases are good for blogs.sun.com, which is a website, but do they make sense for Roller, which is a product? Sun can't force Roller to make monthly releases, since it's an external and independent project, but should the Roller team try to align with the blogs.sun.com release schedule? Is a monthly release too much for an open source web application like Roller? What if Sun was shipping a jazzed-up version of Roller, would Sun want to ship that once a month?
I'm thinking monthly releases a too much for a product like Roller, but I could be convinced otherwise. What do you think?
Raible: If you're hosting your open source project at java.net, you might be annoyed by the fact that you can't disable the forums or issue tracker. The forums pretty much suck, mainly because there's no "remember me" on the site and it's a pain to click 3 times just to answer someone's question. They also don't have the ability to quote a previous message. In addition to the less-than-adequate forums, the issue tracker doesn't hold a candle to JIRA. For the longest time, I've been wanting to remove both the "Discussion forums" and "Project issues" links from the AppFuse homepage. I asked the java.net folks, and they didn't have a solution. Finally, I thought of one on my own.Matt offers some constructive critcism of java.net (and by extension CollabNet).
Roller is not a commercial product with a revenue stream, so itâs difficult to justify the added expense of supporting lots of application servers and databases. As you said, Roller uses Hibernate and should therefore work with any JDBC capable database, but somebody has to write the installation guides and answer the tech support database questions for each platform â if youâd like to volunteer to do that for Weblogic/Oracle, weâd love it! And, if you do get Roller working on Weblogic and Oracle please submut patches to the dev-list so that others donât have to suffer through the porting process too.
Hippified jewelry store in downtown Boone, NC (taken at dusk). Boone, by the way, was named after frontiersman Daniel Boone, who once camped here. According to Wikipedia, Boone claimed to have killed a Yahoo, which is "a vile and savage creature, filthy and with unpleasant habits."
I don't see the notice on Josh's site, so I'll post it here: Join us tomorrow (Tuesday, July 19) for the fortnightly Raleigh/Cary Bloggers meetup.
What: An open meeting to talk about blogging, podcasting & whatever's on your mind
When: Tues @ 6:30 p.m.
Where: Cafe Cyclo, in Cameron Village
2020 Cameron St
Raleigh, NC 27605 (map)
Who: Bloggers & people who want to blog (Podcasters welcome!)
Hope to see you there!
One of the other things I did over the break was to start reading Core JSF again. I've made it about halfway through this time and I must say, the book is quite good. I like the way Geary and Horstmann walk you through the learning process. Starting with something small, simple and not IDE specific and slowly adding in the pieces you need to build a real app. For me, that approach dispelled the "JSF is too complex argument." I'm finding that JSF is a lot less complex than Struts, which is really all I have to compare it against. I might actually finish the book this time ;-)
At JavaOne, I picked up a copy of Java Creator 2 early access (EA) and I've been playing with that as well. I was hoping to build a simple JSF front-end for Roller, just for fun. Creator looks great and the form designer works well, but when I noticed how many com.sun.* classes end up in the generated code I backed off. According to the release notes the whole JSF implementation and com-sun-web-ui-appbase jars are redistributable (as are mail.jar and activation.jar -- that's news to me), but the idea of IDE specific code makes me uncomfortable -- especially in an open source context. So instead of using the form editor, I decided to base my little RollerFaces experiment on example code from Core JSF, which so far relies only on the javax.faces packages.
I decided not to use the form editor, but I didn't want to give up on Creator completely. So I tried to use Creator in place of Netbeans, but ran into another problem: Creator 2 EA only supports the Sun Java App Server and the built-in Netbeans Tomcat launch/debug feature has been disabled. That's disappointing. I don't want or need a full-blown EJB app server for this simple learning excercise. I want Tomcat. It's light-weight, starts fast and I know it well (as do most Java webapp developers, I expect). According to the Creator EA 2 docs, Tomcat support is coming soon. Personally, I would have supported Tomcat and simple webapps first and then Sun Java App Server and more advanced EJB stuff later. Please the most folks first, right? Anyhow, I backed off of Creator 2 EA entirely and now I'm hacking RollerFaces in Netbeans 4.1. I'll try Creator 2 again when it hits beta.