porting old DatabaseAction to modular DatabaseAction

Ah, the eccentricities of legacy code. We are porting an old pre-2.0 Cocoon app over to latest and greatest (Oracle 8i => 10g, Cocoon 2.0 beta => 2.1.9, etc). We've worked out and around most of the issues, but one that I thought would be trivial has stumped the developer and I couldn't find a go

FAQ? Help with Tomcat5, JDK1.5 and Cocoon2.1.9 playing nice together

I have a system I am porting from Cocoon pre-2.0beta, currently running under Tomcat3 and jdk1.3, to later and greater (Tomcat 5.0.30, JDK 1.5.0.6, Cocoon 2.1.9). (Don't ask...) I've read the "upgrading older" document and using ParanoidCocoonServlet did solve a big issue we had. However, even af