Remember the Tomcat woes I was experiencing on Monday? Well, I think I've figured it out! It wasn't too hard, all I had to do was read the error message ...
java.lang.ClassNotFoundException:
org.apache.webapp.admin.ApplicationServlet
... and go looking. Sure 'nough, this class is not there, nor are any of the other classes for the admin webapp! So I've logged the bug and now I wait. Maybe this is intentional, but I doubt it.
Later: The workaround I'm using is that there's a milestone build from October 14th that has the admin app intact and no errors on startup.
I've decided that I need a new name for struts-xdoclet. "Struts-XDoclet" is just too hard to say - try it, you'll see. Four syllables is just too many. Since I intend for it to be a Struts/XDoclet Jumpstart Kit, I'd like something that tries to signify that, but then again, I like POGN - Plain Old Good Names. SXJK is just as hard to say as Struts-XDoclet. I was thinking SASSY (Struts App Start ... nothing for S and Y) might be a good one - but doesn't really explain much. It'd be cool to name it Abbie, after my daughter, but I don't think sxd (hey, that might be a good one) will be that earth-shattering, and if I'm going to name something after Abbie - it better be good! I just asked Julie and her idea is to name it "struggle" - that's not bad. It eliminates the struggle in building a new webapp. Please comment your suggestions if you have an opinion.
