This is verging on a discussion that may be more appropriate on the OpenInteract mailing list (see Sourceforge), but...

The main OpenInteract website is openinteract.org rather than .com. I'm not sure what the status of the .com website is -- I'll look into it.

P5EE is (or will be) really an interface rather than something you can use directly. That is, if OpenInteract were a P5EE-compliant web application container, you could create an application to run there and it would also run in the libservlet or the aforementioned OpenFrame containers as well.

From what I've seen, porting an existing CGI::Application project to OpenInteract would entail some work but it wouldn't require a rewrite. One feature they both have in common is a action (in OI a handler, in CGI::Application a script) that has multiple operations (in OI a task, in CGI::Application a run mode). So you might have a 'user' action that has the tasks 'search', 'show', 'edit', 'remove'. I think OI has this more centralized than CGI::App, but I'm not certain.

However, if you're using CGI::Application right now and it works well for you, you should probably consider sticking with it and making your application mod_perl-friendly if necessary. OpenInteract has a number of other features -- like object/datasource mapping, authentication, security system, components, theming, etc. -- that for a small development team might require a steeper learning curve that is better spent on making the app work. (Depends on the size of the team, looming deadlines, etc.)

Not to discourage you from using OI, it's just that I hate to see people throw away work that's doing what it's supposed to do :-)

Chris
M-x auto-bs-mode