I'm sure it's me, but with the slightly more than cursory picking-at I've been giving it, I'm disappointed to say that the JBoss Portal probably won't meet my needs either.

It looks great, but it's looking more like the content is meant to be viewed in the portal application more than it seems that the application can be used to maintain other web stuff on the server.

You may find yourself wondering what in the heck am I doing or running into that I can't get any of these otherwise fine pieces of software to work. Really it's the combination of sites on one server. On this box, and directly related to me, I run, of course, jkwarren.info, softwarebyjeff.com, and other sites that I'm not in charge of like the already linked pdblack.twistedpair.net web log. All of these sites are passed through the same Apache web server installation, and each is maintained by scripts on the site and static pages. I also run Tomcat on the server as part of the JBoss installation, and am working to pass that through the Apache server, so it should become transparent to web visitors when they need Java pages, just like it is when the script requires PERL, PHP, or one of the other CGI environments already handled by Apache.

What I'm trying to do with this other integration is have some way, via web pages if at all possible, to maintain the website. Preferably something that would ease the editing of static web pages or existing scripts, uploading of new pages, scripts, Java archives, images, moving these files, and the deletion of old items, too. Microsoft FrontPage works swell on IIS servers, but I've moved away from Microsoft, if for no other reason than I don't want to have to license FrontPage on every workstation that I use.

It looks like I might be stuck writing such a content management system, it appears. Until then, I'll keep playing with the JBoss Portal, and the other software I already use.