Yeah, this means that either there is no mapping for one of the classes
that you are trying to save, or that the target ObjEntity is marked as
"read-only".
The message is indeed confusing. I will update this section of code to
have a more meaningful message. If you have other examples of confusing
exception messages in that f*king Cayenne, please file a bug so that we
could address it :-)
Andrus
>
> if (readOnlyObjEntities.contains(objEntityClass)) {
> return false;
> }
>
> if (!writableObjEntities.contains(objEntityClass)) {
> entity = classifyAsWritable(objEntityClass);
> if (entity == null) {
> return false;
> }
>
> so it seems related to modifying read-only objects ?
>
> regards,
>
> Arndt
>
> BTW, hows life at Saclay? I worked at "Laboratoire Nationale Saturne"
> for my thesis for some time before the Synchrotron was shutdown in 1997.
> (I really miss the bad coffee in the breakfast restaurant...)
>
>
>
>
>
> Jean-Paul Le Fèvre wrote:
>
>>As usual it is really hard to guess why a f*king cayenne application
>> fails (!*.. !
>>
>>The exceptions thrown are never very specific : most of the time
>>it is a CayenneRuntimeException with a cause which remains unclear.
>>
>>I've been spending my day trying to figure out why my program
>>no longer works. The trace is the following :
>>
>>Cause : [v.1.0b3 May 25 2003] Classification failed !
>>org.objectstyle.cayenne.CayenneRuntimeException: [v.1.0b3 May 25 2003]
>> org.objectstyle.cayenne.CayenneException: [v.1.0b3 May 25 2003]
>> Classification failed
>> at
>> org.objectstyle.cayenne.access.DataContext.commitChanges(DataContext.java:735)
>> at
>> org.objectstyle.cayenne.access.DataContext.commitChanges(DataContext.java:706)
>> at hep.xmm.l3sdb.data.UserHandler.addRole(UserHandler.java:229)
>> at hep.xmm.l3sdb.client.UserManager.run(UserManager.java:258)
>>
>>Thank you for any help,
>>
>>
This archive was generated by hypermail 2.0.0 : Tue Jun 24 2003 - 11:44:34 EDT