This content has been marked as final. Show 2 replies
I recently upgraded from 3.2.1 to 3.2.3. Using Oracle, a CMP bean returns a date data type from a read-only view as a java.util.Date. In 3.2.1, this worked fine; with 3.2.3, it appears that JBoss is attempting to update the column in the database. Since this is a read-only view, Oracle throws an exception because the column should not be touched - I'm only using a getter. Other data types work as expected, only the date field is a problem.
Does anyone know what changed between 3.2.1 and 3.2.3 that might cause this problem? Before anyone suggests it, the view is staying for any number of reasons. Regardless, I believe this should work and am looking for some direction on why this does.