On 5/5/06, Chris Chiappone <[EMAIL PROTECTED]> wrote:
I should have mentioned that our homegrown framework is EJB and jsp's. Would there be any issue with tapestry accessing the EJB's. I'm used to hibernate but I don't see it working in this project mainly because of the large database size, and the fact that keeping hibernate in sync with any changes to the database that I don't have control over would be frustrating.
I'm not sure to understand your issue with hibernate... Hibernate will keep in sync data the way you configure it. We just implemented a 150 tables (with billions of rows) app with hibernate... The learning curve is more than step though but there is hardly anything you can't achieve with hibernate. Anyway this shouldn't have any impact with your tapestry integration... Tapestry is not tied to any data layer. I just mentioned Spring because it has built-in mecanisms to share data accross servlets and filters. Henri.
