Try doing the mapping files yourself. That's what I've done and I was up and running with Hibernate very quickly. The relationships are a little tricky, but not really too bad, and the documentation is pretty good. If all else fails, the source is always there.
You may just need to study up on XDoclet. It seems simple enough but then again I haven't taken the time to learn it :D
I thought about doing it that way, but keeping separate mapping and class files seems like too much maintance for a production app. And after spending many unsuccessful days simply trying to get XDoclet to generate mapping files, learning Hibernate is just no longer in our budget...at least for this project. I'll keep tinkering with it on-the-side, but for now I need to produce some results direcly with JDBC.
Thanks for your encouragement--I do appreciate all ideas.
If you already have POJOs and the code is well tested, then converting them to DAOs is cost-effective and quick. Particularly if the data model is stable and not likely to change greatly. Otherwise you would use entity beans or Hibernate to accommodate rapid change easily. Common sense rather than FAD should rule. MHO.