Hi.
Sorry for all that stuff. Finally I solved the problem by simply setting
the property
ImplicitLocking=true
in OJB.properties
Thank you so much for your patience.
--
José María
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
Hi again.
>> Hi.
>>
>> I've been testing the CVS
>
> A typo? We moved OJB from CVS to SVN long time ago.
Yes. I meant SVN, sorry.
>
>> version of OJB to solve a problem we have with
>> one of our applications. It seems that in memory locking is not working
>> properly. Here's some trivial test c
Hi.
I've been testing the CVS version of OJB to solve a problem we have with
one of our applications. It seems that in memory locking is not working
properly. Here's some trivial test case.
package com.whatever;
import java.util.List;
import junit.framework.*;
import org.apache.ojb.odmg.OJB;
im
Armin Waibel escribió:
> Jose Maria wrote:
>>> If this doesn't solve your problem, please let me know (then I will
>>> try to reproduce your problem with a test-case).
>> I've done that. Setting auto-update/delete to 'none'. But it still
>> f
Armin Waibel escribió:
> Hi Jose,
>
> I reviewed your example and now I'm confused. You define the relation
> between A and B as 1:n, but in metadata descriptor you set the PK of B
> as FK in 1:n relation
>
> auto-retrieve="true" auto-update="false" auto-delete="false">
>
>
>
> In this
Armin Waibel escribió:
> Hi Jose,
>
> since version 1.0.2 the mandatory auto-update/delete settings are 'none'
>
>
> - odmg-api: ** All relations (1:1, 1:n and m:n) need
> auto-update/delete setting 'none' to proper work.**
>
>
> In 1.0.4 we introduce cascading delete for auto-delete, please see
Hi.
I've recently updated from OJB 1.0.3 to 1.0.4 and I'm having with the
ODMG API. What worked in 1.0.3 now doesn't. It seems to be a change in
the states classes, but I'm not sure. In short, the problem could be
explained with a simple example.
We have two classes A and B, related 0:N. If I cre
Hi all. I've been some time testing with OJB rc4 and now I'm trying it
in production environment, but i'm having some troubles.
The system it's a tomcat struts-based application. The user interact
finally ends with a interaction with an object with methods like
"getProductCollection" or "updatePro
