hi serge
In previous posts I was refering to JCR-63 #10, sorry for not being more careful.
Now. I think that the error log you sent in a previous mail was not caused by a problem in the PM implementation. The exception is thrown when the test is succesful.
The XATest says:
// assertion: commit must fail since integrity violated
try {
utx.commit();
fail("Commit succeeds with violated integrity");
} catch (RollbackException e) {
/* expected */
}So, I think you shouldn't worry for this error. Or am I missing something?
Regards edgar
Edgar Poce wrote:
hi serge
Sorry, I was absolutely wrong :(. I'll take a look at the sources you uploaded ASAP.
regards Edgar
Edgar Poce wrote:
hi serge
Serge Huber wrote:
I'm still having the problem of the references not being properly processed. If anybody has any idea what's going on (it happens in both PersistenceManager implementations) I'd be very grateful as I don't have all that much time to spend on this.
I think that in OJB the references are handled properly. In hibernate you have to call destroy(NodeReferences) and then store all the modified references. It's not a good solution, but I don't know of any better until the references handling is modified.
I added this line in OJB:
// destroy all the references before saving destroy(refs, broker);
// Store part ...
Regards, Serge Huber.
regards edgar
