I posted previously about a "Can not persist java.lang.Integer" error in hibernate. However, it now seems that this was a red herring -- thrown to indicate that a class entry is not found in the hibernate mapping file.

Without my touching it, the "Can not persist" errors went away and the site worked (hence my belief that it just couldn't find the entry in the mapping file). However, now that the code has been moved onto our production servers. I am, once again, seeing this problem.

Despite having the same code running on the same version of hibernate, I am seeing the error on our production servers but not seeing it on my development box.

Does anyone know how I can force hibernate to re-load the mapping file? Does anyone have any other suggestions?