Mailing-List: contact user-help@cayenne.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cayenne.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Message-ID: <47848B21.2060108@ptbsl.com>
Date: Wed, 09 Jan 2008 09:51:45 +0100
From: =?ISO-8859-1?Q?=C1lvaro_Mart=EDnez?= <alvaro_martinez@ptbsl.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: user@cayenne.apache.org
Subject: Re: Selective commit
References: <47821E96.1060703@ptbsl.com>
	 <B6584D41-23BB-4AD5-9D89-9EBFC1077636@objectstyle.org>
	 <47824585.7090001@ptbsl.com>
 <f65b8ae30801070743p18135e5cxe4272554971d64b1@mail.gmail.com>
 <47838331.3010403@ptbsl.com>
 <88187E68-1ADF-4C98-8234-2EE416E225C6@objectstyle.org>
 <478384A1.8030205@ptbsl.com>
 <B4B17649-DC7C-4EF4-B507-433735274ED1@objectstyle.org>
 <478393B0.10708@ptbsl.com>
 <3EE2D49B-A329-4A4E-9725-49C593041388@objectstyle.org>
 <4759D4A8-502F-479E-97EE-BBE7C4AA56B9@objectstyle.org>
In-Reply-To: <4759D4A8-502F-479E-97EE-BBE7C4AA56B9@objectstyle.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit


Using brand new data contexts solved the problem! I just replaced this 
function:

    public DataContext getNewContext() {
        DataContext newContext = context.createChildDataContext();
        newContext.setTransactionEventsEnabled(true);
        newContext.setValidatingObjectsOnCommit(true);
        return newContext;
    }

With this one:

    public DataContext getNewContext() {
        return DataContext.createDataContext(true);
    }

And everything is ok now. I didn't touch any other piece of code.

Thank you very much!


Andrus Adamchik escribi�:
> BTW, while I am investigating the bug with nested contexts ... do you 
> have to use them at all? Can you just use multiple peer DataContexts 
> instead?
>
> Andrus