Description of problem: When starting a CCM server no checks are made to ensure that the database schema version is consistent with the version of the JARs containing the application code. If the two get out of sync the result will at best be a sysstem which throws errors in various places, at worst the objects / metadata stored in the database will become corrupt. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Install & load ccm-portal version 1.0 2. Install portal 1.2, but don't run upgrade scripts Actual results: The server starts up normally, but errors are thrown when trying to view the portal applications Expected results: The server startup throws a SevletUnavailbleException with a message indicating that the DB needs upgrading. Additional info:
Closing old tickets