[
https://issues.apache.org/jira/browse/DIRSERVER-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSERVER-1150:
-----------------------------------------
Fix Version/s: (was: 1.5.3)
1.5.4
Not easy to fix.
Here are some ideas :
(01:54:38 AM) [EMAIL PROTECTED]/Gaim: if I check the attribute before deleting
it$
(01:54:47 AM) [EMAIL PROTECTED]/Gaim: and thrown a NoSuchAttribute exception
(01:54:52 AM) [EMAIL PROTECTED]/Gaim: it works well,
(01:55:05 AM) [EMAIL PROTECTED]/Gaim: but the changelog is splitting chunks
(01:55:18 AM) [EMAIL PROTECTED]/Gaim: because we already stored the reverted
operation,
(01:55:25 AM) [EMAIL PROTECTED]/Gaim: assuming that the attribute exists
(01:55:32 AM) [EMAIL PROTECTED]/Gaim: which is obviously not the case
(01:55:45 AM) [EMAIL PROTECTED]/Gaim: so when we try to revert to pass to the
next test,
(01:55:48 AM) [EMAIL PROTECTED]/Gaim: kaboom !
(01:56:14 AM) Alex Karasulu: well then preload the entry in changelog service
before making the decision to determine what the proper reverse operation will
be
(01:56:50 AM) [EMAIL PROTECTED]/Gaim: I think we should revert the revert if we
have an exception
(01:56:59 AM) Alex Karasulu: yeah good point
(01:57:04 AM) Alex Karasulu: we have to
(01:57:12 AM) Alex Karasulu: that's another thing that we do not do
(01:57:12 AM) [EMAIL PROTECTED]/Gaim: or that we don't apply the revert if we
get an exception
(01:57:27 AM) Alex Karasulu: we need transactions here
(01:57:39 AM) [EMAIL PROTECTED]/Gaim: anyway, the modify/add/delete operations
have to be reviewed from top to the bottom
> No error thrown when removing a non existing value of an attribute
> ------------------------------------------------------------------
>
> Key: DIRSERVER-1150
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1150
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.1
> Reporter: Pierre-Arnaud Marcelot
> Assignee: Emmanuel Lecharny
> Fix For: 1.5.4
>
>
> It's possible with Apache DS 1.5.1 and the latest trunk to execute a request
> where you remove a non existing value of an attribute.
> This request return a SUCCES response.
> I think an Error Response should be returned instead, as OpenLDAP does,
> indicating that the value does not exist.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
