BTW - Normally I would just check in all the tests
and stuff, and point to them in the JIRA, but
I'm changing stuff every 5 minutes, so I figured
I'd just wait and do 1 massive check in.
Emmanuel Lecharny (JIRA) wrote:
[ https://issues.apache.org/jira/browse/DIRSERVER-947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499367 ]
Emmanuel Lecharny commented on DIRSERVER-947:
---------------------------------------------
Ole,
can you use new BasicAttributes(true) instead of the same constructor without
argument and tell us if it's better ? Thanks !
Add an Ole Exception
--------------------
Key: DIRSERVER-947
URL: https://issues.apache.org/jira/browse/DIRSERVER-947
Project: Directory ApacheDS
Issue Type: Improvement
Environment: FC6
Reporter: Ole Ersoy
Priority: Minor
I cleaned up all my tests and made everything perfect, birds singing,
children laughing, etc.
Just to make sure everything is tight, I run the tests
one more time.
I get this exception:
javax.naming.NamingException: [LDAP: error code 80 - failed to add entry
m-oid=1.3.6.1.4.1.18060.4.55101545.5251491.1569756.3515752.5985152.5551015.5055525.50101501.052,ou=attributeTypes,cn=das,ou=schema:
Unexpected exception.]; remaining name
'm-oid=1.3.6.1.4.1.18060.4.55101545.5251491.1569756.3515752.5985152.5551015.5055525.50101501.052'
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3049)
Yeah - It's definitely unexpected.
What's up with thiiis?
Turns out I left one of methods like this:
objectClassAttribute.add( META_TOP );
basicAttributes = new BasicAttributes();
basicAttributes.put(objectClassAttribute);
basicAttributes = new BasicAttributes();
basicAttributes.put( M_OBSOLETE, LDAP_FALSE );
....
blah blah blah
See it? I restarted my basic attributes (And put blah blah blah right in the
code).
Can we have a better exception being thrown for this?
I was thinking an Ole Exception with description "Ole, or someone pretending to
be Ole, messed the code up biggg time!
Go fix the attributes then talk to me".
Cheers,
- Ole
