Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 61608 invoked from network); 18 Jan 2007 16:51:52 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 18 Jan 2007 16:51:52 -0000 Received: (qmail 49119 invoked by uid 500); 18 Jan 2007 16:51:58 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 49094 invoked by uid 500); 18 Jan 2007 16:51:57 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 49083 invoked by uid 99); 18 Jan 2007 16:51:57 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Jan 2007 08:51:57 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Jan 2007 08:51:50 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id B86B77142BF for ; Thu, 18 Jan 2007 08:51:30 -0800 (PST) Message-ID: <9299838.1169139090752.JavaMail.jira@brutus> Date: Thu, 18 Jan 2007 08:51:30 -0800 (PST) From: "Emmanuel Lecharny (JIRA)" To: dev@directory.apache.org Subject: [jira] Commented: (DIRSERVER-758) schema checking In-Reply-To: <8798001.1160245579869.JavaMail.root@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DIRSERVER-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465808 ] Emmanuel Lecharny commented on DIRSERVER-758: --------------------------------------------- I confirm that there is no such control in ADS. You can define any attribute you want without any limitation. Oh, btw, seems to be a bug :( > schema checking > --------------- > > Key: DIRSERVER-758 > URL: https://issues.apache.org/jira/browse/DIRSERVER-758 > Project: Directory ApacheDS > Issue Type: Bug > Environment: windows xp > Reporter: mbah tenjoh-okwen > Priority: Minor > > Hi, > I understand that "LDAP directories use the concept of object classes to > define which attributes are allowed for objects of any given type" > consequently , I would like to know if the following behavior is normal: > in ApacheDS I am able to make use of any attribute without having added > the object classes which provide these attributes. > Illustration > say I have an entry uid=kevin, ou=users,ou=sample > kevin has the following attributes cn=kevin spacey, dc=ke, objectclass=top > Is it normal for apacheDS to allow me add cn and dc attributes even > though I havent added the object classes Person and domain ? > Please start a new thread when you change the topic. > Schema checking should prevent this if it is enabled and by default it > is in ApacheDS. If it's not doing that then we have a bug. > here is the code > public class CreateSubcontext { > /** > * @param args > */ > public static void main(String[] args) > { > try > { > //use properties file to set connection > InputStream inputStream = new FileInputStream( "apacheds.properties"); > Properties properties = new Properties(); > properties.load(inputStream); > > > //create context > DirContext ctx=new InitialDirContext(properties); > > //mould entry > Attributes attrs=new BasicAttributes(true); > Attribute obj=new BasicAttribute("ObjectClass", "top"); > Attribute ob = new BasicAttribute("cn", "kevin Spacey"); > Attribute ob1 = new BasicAttribute("dc", "ke"); > attrs.put(obj); > attrs.put(ob); > attrs.put(ob1); > String rdns="uid=kevin"; > > //create subcontext > DirContext result=ctx.createSubcontext(rdns, attrs); > result.close(); > }catch(Exception e) > { > System.out.println(e); > } > } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira