[DIRSERVER-947] Add an Ole Exception

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: 1.5.0
• Fix Version/s: 1.5.2
• Environment: FC6
• Assignee: Unassigned
• Reporter: Ole Solberg
• Created: 26/May/07 20:59
• Updated: 02/Dec/08 23:02
• Resolved: 02/Apr/08 23:02

Description

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