Hi Jonas support team,
I upgraded my Jonas version 2.2.6 to 2.3. All was very easy (thanks!),
except for a
duplicate key exception I am encountering now.
Situation is as follows. If an entry of table is updated the entry is
first deleted
and then inserted. This is necessary, as sometimes the key of the entry
is changed.
If the key is changed, the delete and insert operation run fine. But if
the key
is not changed, a DuplicateKeyException is raised. While the entry is
not anymore
available in the database. In release 2.2.6 the DuplicateKeyException
was not raised.
I did some tests to check this.
How can I solve this problem? I tried to set the transaction attribute
to 'RequiresNew',
but that did not solve the problem. And why does it occur in version 2.3
and not
in version 2.2.6? I checked the mailing list, but did not see this
problem mentioned.
I would appreciate your opinion on this matter.
Sophie
----
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe jonas-users".
For general help, send email to [EMAIL PROTECTED] and
include in the body of the message "help".
