I ran into a case where the whole tapestry web app fails to start if it is 
unable to log into any database.I believe it should be resilient enough to be 
able to at least catch the failure in a nice error page.Right now, if 
EclipseLink fails to initialize, the whole web app, whether it relies on that 
particular database or not,is inaccessible.Databases are configure in 
persistence.xml file.Thanks!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

Reply via email to