Why do I get an ObjectModifiedException when trying to commit a transaction?
The dirty checking engine will throw an ObjectModifiedException when the values in the cache and in the database are different. This can happen when someone else changed the database content, but also when type mapping is not reversible. For example, if a java timestamp (java.util.Date) is stored as a DATE, the time part is lost and the dirty checking will fail. Oracle cannot tell the difference between an empty String and a null value: if an attribute value is an empty String, dirty checking will also fail. Some precision loss sometimes occur with floating point numbers. To avoid this, always use reversible mapping conversions. If this is not possible, mark the fields with dirty=”ignore” in the mapping file. I’m receiving a java.sql.SQLException: ORA-01461 When using Weblogic Portal 4.0 with Oracle I am receiving the following error: java.sql.SQLException: ORA-01461: can bind a LONG value only for insert into a LONG column According to Weblogic Release Notes, this error can remedied b
