Hi Robert,
Although the causes of client-side CayenneContext problems are likely
different from the server-side DataContext, this part of the stack
was reworked recently as well, so there may be glitches. Please
provide more info when you have a chance. In the meantime I'll
include extra diagnostics in the exception message.
Andrus
On Apr 13, 2006, at 9:08 AM, Robert Zeigler wrote:
Interesting...I also had faulting issues with 1.2B1. (past tense
because
I needed a fix very fast; so I downgraded back to M5, which is what I
was using before). The error I was getting wasn't a "toMany"
relationship, though. But, the behavior there was also a bit
stochastic... sometimes it worked, and sometimes it didn't; in May,
things will be in more of a position for myself (and also for the
company using the software) to where I can dig deeper into this. In
the
meanwhile, this is the exception I was getting:
org.objectstyle.cayenne.FaultFailureException
[v.1.2B1 April 6 2006] Error resolving fault, no matching row
exists in
the database for ObjectId: <ObjectId:AssignmentParameters,
assignmentid=1590>
unlabeledMessage: Error resolving fault, no matching row exists in
the
database for ObjectId: <ObjectId:AssignmentParameters,
assignmentid=1590>
Stack Trace:
* org.objectstyle.cayenne.access.DataContext.prepareForAccess
(DataContext.java:1742)
* org.objectstyle.cayenne.CayenneDataObject.readProperty
(CayenneDataObject.java:238)
*
org.eledge.domain.auto._AssignmentParameters.getPermitInvalidTransacti
ons(_AssignmentParameters.java:68)
* org.eledge.domain.Assignment.assignmentDoable(Assignment.java:
49)
*
org.eledge.components.AssignmentTransactionCreator.doTransaction
(AssignmentTransactionCreator.java:23)
* org.eledge.pages.ViewAssignment.activateExternalPage
(ViewAssignment.java:32)
