Looks like the message text was removed between version 1.2 and 2.0. I've restored it in trunk and I'll put it back in 2.0 and 2.1 too.
Thanks for reporting the problem. -mike On Mon, Feb 7, 2011 at 3:50 AM, Jean-Baptiste BRIAUD -- Novlog < j-b.bri...@novlog.com> wrote: > Hi the list, > > I got the following exception : > Caused by: <openjpa-2.0.1-r422266:989424 nonfatal user error> > org.apache.openjpa.persistence.ArgumentException: cant-set-value > at > org.apache.openjpa.jdbc.meta.strats.HandlerFieldStrategy.insert(HandlerFieldStrategy.java:132) > at > org.apache.openjpa.jdbc.meta.FieldMapping.insert(FieldMapping.java:623) > at > org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.insert(AbstractUpdateManager.java:230) > at > org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.populateRowManager(AbstractUpdateManager.java:162) > at > org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:95) > at > org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:76) > at > org.apache.openjpa.jdbc.kernel.JDBCStoreManager.flush(JDBCStoreManager.java:731) > at > org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:131) > ... 35 more > > Would it be possible to add the field/column name which the value can't be > set ? > >
