[
https://issues.apache.org/jira/browse/DIRSERVER-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13000280#comment-13000280
]
Pierre-Arnaud Marcelot commented on DIRSERVER-1610:
---------------------------------------------------
I added a new test case for this issue:
org.apache.directory.server.operations.add.AddIT.testAddEntryNonExistingAT()
The test is ignored for now, to avoir build breakage.
> No error is reported when adding an entry with a non-existing attribute
> -----------------------------------------------------------------------
>
> Key: DIRSERVER-1610
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1610
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.7
> Reporter: Pierre-Arnaud Marcelot
> Priority: Blocker
> Fix For: 2.0-M1
>
>
> It is possible to add a new entry with a non-existing attribute successfully
> ('success' result code).
> This error only occurs when adding an entry with the network layer, not with
> direct CoreSession.
> For the record, here's what we debugged with Emmanuel.
> The entry is correctly decoded and received by the AddHandler.
> Then that entry is cloned in the AddOperationContext and it's during the
> creation of that clone (DefaultEntry.clone() method) that the non-existing AT
> is excluded of the cloned entry without notifying an error and swallowing the
> exception.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
