Raible Designs

Struts Resume 0.5 Released!

I was up until 7:00 a.m. this morning finishing the struts-resume example application for my Struts chapter. I finally did it - I'm done. At least for now. I'd love to set a demo up on this server, but it requires a MySQL database, and I don't want to pay Keith the $20 to setup another database instance for me. I know, I know - Why don't I use HSQL? Because I just finished the damn application, and I need to convince myself to not touch it for at least a few days, or I'll never get anything else done (like cleaning my desk and hitting the gym).

Short-term (next 2-3 week) goals for this project are:

• Abstract the good stuff out of struts-resume for AppFuse. They're really the same thing right now, and I'll need to trim it down a bit so there's only CRUD on a user or something like that.
• Get it into the Struts Project's CVS at SourceForge.net. Ted Husted made me a committer, now I just have to do it. I'd rather check in appfuse than struts-resume, so the previous step is a must.
• Change Struts to use path-mapping (/do/*) rather than extension-mapping (*.do). The tricky part is making this work with modules.
• Code cleanup and Javadocs. Use checkstyle to make everything peachy-keen.

I don't believe it's important to fully flush out the features in the application at this point - that might overwhelm users in the end - maybe in a couple months I'll get around to doing that. You can bet I'll get super motivated right around the time I'm looking for a new gig! I'm expecting this in June, so might be awhile.

PMD and Checkstyle

I knew about Checkstyle, but PMD is new to me. The Struts Development Team has recently added these tasks to its build.xml file if you're interested in an example. Erik Hatcher has the Checkstyle task in his JavaDevWithAnt project, and I'm using his build.xml file as a model, but I've never used the Task. I've also had the Checkstyle Plug-In for Eclipse installed at one point, but it gave me so many errors - I disabled it. It'd be nice to use these from the beginning on a project.

[ANNOUNCE] StrutsTestCase v1.9.5 Released!

StrutsTestCase v1.9.5 improves support for Struts 1.1b3 (including support for testing Tiles and sub-applications), provides several requested enhancements, and fixes many reported defects.

For your clicking pleasure, check out the project's homepage or view the release notes.

Using Both Ant and Maven

Erik Hatcher makes a request to get his JavaDevWithAnt project converted from using Ant to Maven:

Ok, a challenge to the Maven or Centipede experts tuning into my blog: make my JavaDevWithAnt project build with either. But the trick is that it has to be simpler than the current Ant build.xml. Believe it or not, I've not (seriously) used either of these tools. I hear the buzz about these and want to become a "believer".

I'm all for this as I've created my AppFuse project using his directory structure/build file as a template. I did go down this path to Mavenism already, but gave up before I finished. My problem is I have 15 different 3rd party JARs I use in my project - many testing frameworks and jakarta stuff. And a lot of these are nightly (or personal) builds because there's been some bug fixed, or enhancement added. What I really want is to continue using Ant b/c I think it rocks and it gives me more control over little tasks, but also to use Maven to generate a project site.

The problem with Erik's request is that I'm guessing no one will jump at the opportunity. Maybe, but in reality, no one looks at each others code unless there's a bug, or they need a sample to get started. Too bad - we could really do wonders for the Java Community if we started reviewing each others code. Erik, maybe you could post little snippets of your build file, and we could convert small parts of it. By posting a measly 10 lines, some other coders might be so inclined to help mavenize it. I know this is not how Maven works, but it sure would be nice if using Maven didn't require abandoning Ant.

Tonight I'll be staying up late trying to finish up AppFuse and Struts-Resume. Since the security-example download seems to be getting a lot of traffic (and it's a 15MB download), I should probably try to get these projects into SourceForge and save myself some bandwidth. Who knows if I'll get it done, I'm pretty tired, and it's already 10:00. But what choice do I have - Saturdays are family days, I promised my client that I pump a bunch of new features out on Sunday, and I get to work an 80 hour-week next week to get our first version out at my new job. Ugh, I need a vacation.

Fighting Technology and Fatherhood

Today was one of those days I hate. I've been struggling with Hibernate for what seems like weeks now. Today was a day that almost convinced me to quit trying. I seem to be fighting with XDoclet and Hibernate all day, every day. I don't seem to be getting anything done on my AppFuse project, nor at my new on-site project.

I am getting things done, but if I'd just done JDBC, I'd probably much further ahead than I am right now. Such is the life of someone that tries to learn the latest technologies. I remember doing this with Struts and now I'm grateful that I did. Hopefully, using/learning/struggling with XDoclet and Hibernate will soon get better. The Hibernate and XDoclet developers have been great in dealing with my learning curve - thanks guys.

I predict my learning curve will be similar as that with Struts. This means that I will write all kinds of code as workarounds for problems I'm having - since I have ridiculous deadlines and I need to get it working. The sad part is that I'm willing to bet that I'll delete a whole bunch of this code when I finally figure out how to work with Hibernate, rather than against it. I think it's a great framework, but I'm trying to do too much from examples, rather than digging in and actually learning the framework. This is the hard way, but alas - I will learn it well - through my own mistakes.

I got a nice break from Technology tonight as Julie and I went to pick up our new car. We drove the long way home - through Red Rocks. We enjoyed the smooth ride, bright lights, and nice stereo. The bug had all of this, but the Accord is newer, and therefore, more fun. We stopped and bought a bottle of wine at one of my favorite liquor stores in Morrison and had a nice little celebration. I was planning on finishing up my struts-resume sample application tonight, but instead decided to play with Abbie. We gurgled and had some "tummy time" - and I definitely feel like I did the right thing.

I think I really need to stop working so much, and start being a Dad more. I've worked every weekend since she was born, and I feel like an Ass for it. Hopefully, the Wrox gig will be over soon, and I'll be able to catch up on my work for OnPoint and relax a little more. All this extra work is wearing me thin, especially when it's been dumping in the mountains lately - I don't know how many more "8 inches at Vail" e-mails I can take!!

The encouraging news (for you, the reader) is that I (with the help of Keith) upgraded this site to use a 100MB connection tonight. Hopefully the site will be a bit faster, but you know how bandwidth works - you pay for more and never seem to get it.

RE: ArrayList vs. Vector - which is better for webapps?

What the hell was I thinking?! I must've been tired this morning when I wrote the last post. I meant to say Serializable not Synchronized!! Yikes - what a blunder! Does this change your feelings? What if I have a UserForm (extends ActionForm) that has an ArrayList of children? I usually put a user's Form in the session, so I can access their information at any time.

[ANNOUNCEMENT] Struts 1.1 Beta 3 Released

The Struts team is proud to announce the release of Struts 1.1 Beta 3. This release includes significant new functionality, while retaining full backwards compatibility with earlier versions of Struts. It also incorporates fixes for a number of bugs which were reported against earlier versions.

The binary distribution is available at:

  http://jakarta.apache.org/builds/jakarta-struts/release/v1.1-b3/

and the source distribution is available at:

  http://jakarta.apache.org/builds/jakarta-struts/release/v1.1-b3/src/

In addition, the library distibution, which contains updated binaries without the sample applications, is available at:

  http://jakarta.apache.org/builds/jakarta-struts/release/v1.1-b3/lib/

Details of the changes in this release are available in the Release Notes, which can be found here:

  http://jakarta.apache.org/struts/userGuide/release-notes-1.1-b3.html

Sweet! Now I can stop downloading the nightly build for a while! Thanks Struts Developers - what a great New Years Eve present!

RE: PlugIns and Struts Nightly Build

It turns out that I didn't need to add the setCurrentPlugInConfigObject method to struts-menu's MenuPlugIn.java. I just needed to compile struts-menu with the latest struts.jar. This told me that the init(ActionServlet, ApplicationConfig) had been removed and I had to implement init(ActionServlet, ModuleConfig). The ApplicationConfig interface has been deprecated in recent weeks in favor of ModuleConfig, but you would think that this method would be deprecated as well, not removed! Oh well, I've fixed my local version of Struts Menu, but don't know how to handle making a Struts 1.1-compliant version, and a Struts 1.0.x-compliant version. Any ideas are appreciated. You can track this issue in Struts' Bugzilla.

PlugIns and Struts Nightly Build

I had a nice frustrating evening tonight trying to get the nightly build of Struts to work with Tiles, Modules and the Struts Menu. Actually, it wasn't a Struts problem so much as a Struts Menu problem. I was getting a java.lang.AbstractMethodError error when hitting the first action class, and couldn't figure out why. I started by bitching to the struts-dev list, and then filed a bug. Eddie Bush was kind enough to suggest that there was something wrong with my PlugIns. I thought - how could there be - I'm using Tiles and Validator? So I looked at my struts-plugins.xml file and there was the culprit - struts-menu. It turns out that I needed to add the following variable and method to MenuPlugIn.java:

/** The plugin config object provided by the ActionServlet initializing
 *  this plugin.
 */
protected PlugInConfig currentPlugInConfigObject;

/**
 * Method used by the ActionServlet initializing this plugin.
 * Set the plugin config object read from module config.
 * @param currentPlugInConfigObject
 */
public void setCurrentPlugInConfigObject(PlugInConfig currentPlugInConfigObject) {
    this.currentPlugInConfigObject = currentPlugInConfigObject;
}

This post was written in hopes of alleviating someone else's troubles with this same problem.

Java Development with Ant, The Application

If you've been fortunate enough to read Erik Hatcher's Java Development with Ant, you know that there's tons of good tips in it. I read it and I've been recommending it every since. Erik has been continuing development of the sample app for the book ever since it was released. I got many tips from Erik in developing AppFuse and I have to say, it really is a nice example. Maybe I'll get some more stuff now that it appears to have jumped from version 0.4 to 0.9! Here's a message Erik sent about the latest release.

All -

I'm proud (and worried about the support e-mails! :) to announce the 
near-final release of a project demonstrating Ant, XDoclet, Struts, 
JUnit, Cactus, and Lucene.  Its called JavaDevWithAnt as it was written 
for the book Steve and I co-authored and has been refined during 
several presentations I've been giving on Ant, XDoclet and Struts.

The documentation is in draft stage, and my primary goal is to collect 
feedback on polishing the documentation (and the application if there 
are any bugs that surface).  The site where I'm hosting the 
distribution and documentation is:

	http://www.ehatchersolutions.com/JavaDevWithAnt/

Please let me know if you try it out and have suggestions for 
improvement, or just to let me know you tried it and hate it or love 
it, etc.  Feedback more than welcome!  Direct feedback to me at 
[email protected]

	Erik

p.s. Since this e-mail is directed to the XDoclet, Lucene, and Cactus 
lists, here is a brief teaser for you:

XDoclet - its used extensively, even using a custom tag handler to 
generate starter JSP's from Struts form beans.

Lucene - my <index> Ant task is used to index text and HTML files, and 
Lucene's API is used at run-time to query the index.

Cactus - StrutsTestCase is used, although no direct Cactus tests.

Happy information-overload! There's a lot there, but if I could figure it out - I'm sure you can. Erik - finally on Jaguar eh? What took you so long ;-)