directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tony Thompson" <Tony.Thomp...@stone-ware.com>
Subject RE: Issue with multi valued attributes
Date Fri, 12 Jan 2007 21:52:32 GMT
Yeah, I went through that bug ticket and it sounds exactly like the
issue I am having.  How soon can I get 1.0.1?  I would rather not go the
route where I have to build this myself. 

-----Original Message-----
From: Ersin Er [mailto:ersin.er@gmail.com] 
Sent: Friday, January 12, 2007 4:49 PM
To: Apache Directory Developers List
Subject: Re: Issue with multi valued attributes

Well I think it has already been fixed (as Stefan said) and you will get
it with 1.0.1. You can also built ApacheDS from source and generate
installers easily to get this fix fast.

On 1/12/07, Tony Thompson <Tony.Thompson@stone-ware.com> wrote:
> 1.0.0  I downloaded it from the website at the end of last October.
>
> -----Original Message-----
> From: Ersin Er [mailto:ersin.er@gmail.com]
> Sent: Friday, January 12, 2007 4:28 PM
> To: Apache Directory Developers List
> Subject: Re: Issue with multi valued attributes
>
> Hi Tony,
>
> Which version of ApacheDS are you using? We recently fixed such an 
> issue.
>
> On 1/12/07, Tony Thompson <Tony.Thompson@stone-ware.com> wrote:
> >
> >
> >
> > I am having an issue with modifying a multi-valued DN type attribute

> > on a user object.  The attribute is a custom schema extension that I

> > added.  If I use an LDAP browser, the first value I add to the 
> > attribute works fine.  The second and subsequent values I add to 
> > that attribute are added twice.  I can also duplicate this by 
> > assigning the
> "member" attribute to the user object.
> > The steps to duplicate this are:
> >
> > - create an inetOrgPerson object
> > - add a "member" attribute with a DN value
> > - add a "member" attribute with a different DN value
> >
> > The second add shows up in the attribute values twice.  Every one I 
> > add after that seems to add twice.  Any idea why this might be?
> >
> > Tony
> >
> > This message (and any associated files) is intended only for the use

> > of the individual or entity to which it is addressed and may contain

> > information that is confidential, subject to copyright or 
> > constitutes a trade secret. If you are not the intended recipient 
> > you are hereby notified that any dissemination, copying or 
> > distribution of this message, or files associated with this message,

> > is strictly prohibited. If you have received this message in error, 
> > please notify us immediately by replying to the message and deleting

> > it from your computer. Messages sent to and from Stoneware, Inc.
> > may be monitored.
> >
> >
>
>
> --
> Ersin
>
> This message (and any associated files) is intended only for the use 
> of the individual or entity to which it is addressed and may contain 
> information that is confidential, subject to copyright or constitutes 
> a trade secret. If you are not the intended recipient you are hereby 
> notified that any dissemination, copying or distribution of this 
> message, or files associated with this message, is strictly 
> prohibited. If you have received this message in error, please notify 
> us immediately by replying to the message and deleting it from your 
> computer. Messages sent to and from Stoneware, Inc.
> may be monitored.
>


--
Ersin
 
This message (and any associated files) is intended only for the 
use of the individual or entity to which it is addressed and may 
contain information that is confidential, subject to copyright or
constitutes a trade secret. If you are not the intended recipient 
you are hereby notified that any dissemination, copying or 
distribution of this message, or files associated with this message, 
is strictly prohibited. If you have received this message in error, 
please notify us immediately by replying to the message and deleting 
it from your computer. Messages sent to and from Stoneware, Inc.
may be monitored.

Mime
View raw message