Announcement Announcement Module
No announcement yet.
Unstable Schema Question Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • Unstable Schema Question


    We have recently re-implemented our website using the spring/hibernate framework.

    We are currently having some teething issues with the framework, specifically relating to database access.

    We often come across an issue such as a varchar field being too small when trying to write data or even the schema being changed in the middle of the night by our illustrious DBA.

    when issues like this arise, we want to hide any errors generated, from the end user (they currently recieve a 500).

    would it be valid and "correct" to extend the HibernateTransactionManager to catch these exceptions (and log them and notify us) and then quietly fail, returning a successful view to the user.

    Obviously the exceptions do not propagate to our controllers due to the proxying of our DAO (i can supply a stacktrace if its of any use).

    Thank for any feedback and suggestions

    cheers, toby