You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Stefan Zoerner (JIRA)" <ji...@apache.org> on 2006/08/07 22:11:13 UTC
[jira] Created: (DIRSERVER-701) Replacing an existing attribute
with an attribute with no values lead to an (illegal) attribute with empty
value
Replacing an existing attribute with an attribute with no values lead to an (illegal) attribute with empty value
----------------------------------------------------------------------------------------------------------------
Key: DIRSERVER-701
URL: http://issues.apache.org/jira/browse/DIRSERVER-701
Project: Directory ApacheDS
Issue Type: Bug
Affects Versions: 1.0-RC4
Environment: * ApacheDS 1.0 RC4 SNAPSHOT
* Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03)
* Windows XP Professional SP2
Reporter: Stefan Zoerner
If someone tries to replace an existing attribute with an attribute with no values (modify op), it is expected that the attribute is removed. In Apache DS (curent 1.0 branch), this is not the case.
The attached test case creates an inetOrgPerson entry and tries to remove the givenname attribute with the following lines:
...
// replace attribute givenName with empty value (=> deletion)
Attribute attr = new BasicAttribute("givenname");
ModificationItem item = new ModificationItem(DirContext.REPLACE_ATTRIBUTE, attr);
ctx.modifyAttributes(rdn, new ModificationItem[] { item });
...
The operation does not cause an error, but afterwards the givenname attribute is still present in the entry (although it does not have any value). It is expected that the attribute givenname does not exist anymore within the entry.
The attached test case demonstrates the situation and passes on the following servers:
* Sun Java System Directory Server 5.2
* OpenLDAP 2.3
* IBM Tivoli Directory Server 6.0
On Apache Directory Server 1.0 RC4 SNAPSHOT, it fails.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DIRSERVER-701) Replacing an existing attribute
with an attribute with no values leads to an (illegal) attribute with empty
value
Posted by "Stefan Zoerner (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-701?page=all ]
Stefan Zoerner updated DIRSERVER-701:
-------------------------------------
Summary: Replacing an existing attribute with an attribute with no values leads to an (illegal) attribute with empty value (was: Replacing an existing attribute with an attribute with no values lead to an (illegal) attribute with empty value)
> Replacing an existing attribute with an attribute with no values leads to an (illegal) attribute with empty value
> -----------------------------------------------------------------------------------------------------------------
>
> Key: DIRSERVER-701
> URL: http://issues.apache.org/jira/browse/DIRSERVER-701
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.0-RC4
> Environment: * ApacheDS 1.0 RC4 SNAPSHOT
> * Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03)
> * Windows XP Professional SP2
> Reporter: Stefan Zoerner
>
> If someone tries to replace an existing attribute with an attribute with no values (modify op), it is expected that the attribute is removed. In Apache DS (curent 1.0 branch), this is not the case.
> The attached test case creates an inetOrgPerson entry and tries to remove the givenname attribute with the following lines:
> ...
> // replace attribute givenName with empty value (=> deletion)
> Attribute attr = new BasicAttribute("givenname");
> ModificationItem item = new ModificationItem(DirContext.REPLACE_ATTRIBUTE, attr);
> ctx.modifyAttributes(rdn, new ModificationItem[] { item });
> ...
> The operation does not cause an error, but afterwards the givenname attribute is still present in the entry (although it does not have any value). It is expected that the attribute givenname does not exist anymore within the entry.
> The attached test case demonstrates the situation and passes on the following servers:
> * Sun Java System Directory Server 5.2
> * OpenLDAP 2.3
> * IBM Tivoli Directory Server 6.0
> On Apache Directory Server 1.0 RC4 SNAPSHOT, it fails.
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (DIRSERVER-701) Replacing an existing attribute with
an attribute with no values leads to an (illegal) attribute with empty
value
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-701?page=all ]
Alex Karasulu closed DIRSERVER-701.
-----------------------------------
Fix Version/s: 1.1.0
1.0-RC4
Resolution: Fixed
Fixes to 1.0 branch in commit revision 429580 and for 1.1 trunk commit revision 429581.
> Replacing an existing attribute with an attribute with no values leads to an (illegal) attribute with empty value
> -----------------------------------------------------------------------------------------------------------------
>
> Key: DIRSERVER-701
> URL: http://issues.apache.org/jira/browse/DIRSERVER-701
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.0-RC4
> Environment: * ApacheDS 1.0 RC4 SNAPSHOT
> * Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03)
> * Windows XP Professional SP2
> Reporter: Stefan Zoerner
> Assigned To: Alex Karasulu
> Fix For: 1.1.0, 1.0-RC4
>
> Attachments: AttributeRemovalByReplacementTest.java
>
>
> If someone tries to replace an existing attribute with an attribute with no values (modify op), it is expected that the attribute is removed. In Apache DS (curent 1.0 branch), this is not the case.
> The attached test case creates an inetOrgPerson entry and tries to remove the givenname attribute with the following lines:
> ...
> // replace attribute givenName with empty value (=> deletion)
> Attribute attr = new BasicAttribute("givenname");
> ModificationItem item = new ModificationItem(DirContext.REPLACE_ATTRIBUTE, attr);
> ctx.modifyAttributes(rdn, new ModificationItem[] { item });
> ...
> The operation does not cause an error, but afterwards the givenname attribute is still present in the entry (although it does not have any value). It is expected that the attribute givenname does not exist anymore within the entry.
> The attached test case demonstrates the situation and passes on the following servers:
> * Sun Java System Directory Server 5.2
> * OpenLDAP 2.3
> * IBM Tivoli Directory Server 6.0
> On Apache Directory Server 1.0 RC4 SNAPSHOT, it fails.
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DIRSERVER-701) Replacing an existing attribute
with an attribute with no values leads to an (illegal) attribute with empty
value
Posted by "Stefan Zoerner (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-701?page=all ]
Stefan Zoerner updated DIRSERVER-701:
-------------------------------------
Attachment: AttributeRemovalByReplacementTest.java
JNDI Test case to demonstrate DIRSERVER-701 ("Replacing an existing attribute with an attribute with no values leads to an (illegal) attribute with empty value")
> Replacing an existing attribute with an attribute with no values leads to an (illegal) attribute with empty value
> -----------------------------------------------------------------------------------------------------------------
>
> Key: DIRSERVER-701
> URL: http://issues.apache.org/jira/browse/DIRSERVER-701
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.0-RC4
> Environment: * ApacheDS 1.0 RC4 SNAPSHOT
> * Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03)
> * Windows XP Professional SP2
> Reporter: Stefan Zoerner
> Attachments: AttributeRemovalByReplacementTest.java
>
>
> If someone tries to replace an existing attribute with an attribute with no values (modify op), it is expected that the attribute is removed. In Apache DS (curent 1.0 branch), this is not the case.
> The attached test case creates an inetOrgPerson entry and tries to remove the givenname attribute with the following lines:
> ...
> // replace attribute givenName with empty value (=> deletion)
> Attribute attr = new BasicAttribute("givenname");
> ModificationItem item = new ModificationItem(DirContext.REPLACE_ATTRIBUTE, attr);
> ctx.modifyAttributes(rdn, new ModificationItem[] { item });
> ...
> The operation does not cause an error, but afterwards the givenname attribute is still present in the entry (although it does not have any value). It is expected that the attribute givenname does not exist anymore within the entry.
> The attached test case demonstrates the situation and passes on the following servers:
> * Sun Java System Directory Server 5.2
> * OpenLDAP 2.3
> * IBM Tivoli Directory Server 6.0
> On Apache Directory Server 1.0 RC4 SNAPSHOT, it fails.
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (DIRSERVER-701) Replacing an existing attribute
with an attribute with no values leads to an (illegal) attribute with empty
value
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-701?page=all ]
Alex Karasulu reassigned DIRSERVER-701:
---------------------------------------
Assignee: Alex Karasulu
> Replacing an existing attribute with an attribute with no values leads to an (illegal) attribute with empty value
> -----------------------------------------------------------------------------------------------------------------
>
> Key: DIRSERVER-701
> URL: http://issues.apache.org/jira/browse/DIRSERVER-701
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.0-RC4
> Environment: * ApacheDS 1.0 RC4 SNAPSHOT
> * Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03)
> * Windows XP Professional SP2
> Reporter: Stefan Zoerner
> Assigned To: Alex Karasulu
> Attachments: AttributeRemovalByReplacementTest.java
>
>
> If someone tries to replace an existing attribute with an attribute with no values (modify op), it is expected that the attribute is removed. In Apache DS (curent 1.0 branch), this is not the case.
> The attached test case creates an inetOrgPerson entry and tries to remove the givenname attribute with the following lines:
> ...
> // replace attribute givenName with empty value (=> deletion)
> Attribute attr = new BasicAttribute("givenname");
> ModificationItem item = new ModificationItem(DirContext.REPLACE_ATTRIBUTE, attr);
> ctx.modifyAttributes(rdn, new ModificationItem[] { item });
> ...
> The operation does not cause an error, but afterwards the givenname attribute is still present in the entry (although it does not have any value). It is expected that the attribute givenname does not exist anymore within the entry.
> The attached test case demonstrates the situation and passes on the following servers:
> * Sun Java System Directory Server 5.2
> * OpenLDAP 2.3
> * IBM Tivoli Directory Server 6.0
> On Apache Directory Server 1.0 RC4 SNAPSHOT, it fails.
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira