Most of my web application utilize some sort of dynamic content editing. There is nothing worse than having to rebuild and redeploy just for a content change.
I store my text in a database and have a dynamic content action which accepts of parameter of page id, article id, etc. I then return the content to be displayed on the page. This method works well with tiles.
I have also had great success creating my own tag library to do the dirty work. Makes it clean and manageable.
It sounds like the only reason you want to use a CMS is to manage content on a single page. This seems like overkill to me, like buying a car for air conditioning.
EDIT:
You could also create an upload
servlet to upload html files and link to them by creating an entry in the database.
[ September 24, 2007: Message edited by: Chris Boldon ]