[#LDAP-4] Translate LDAP error codes

Spring LDAP

Translate LDAP error codes

Created: 07/Oct/06 12:39 PM Updated: 12/Jan/07 10:36 AM

Component/s:

None

Affects Version/s:

1.1

Fix Version/s:

1.2-RC1

Time Tracking:

Not Specified

File Attachments:

None

Image Attachments:

1. NamingException.png
(63 kB)

Description

« Hide

The ExceptionTranslator could be improved to also automatically parse the error code and retrieve the corresponding readable message.

All

Comments

Work Log

Change History

FishEye

Builds

Sort Order:

[ Permlink | « Hide ]

Ulrik Sandberg added a comment - 18/Dec/06 03:20 PM

Looking more closely at this issue, there are some things to consider. The main reason the DataAccessException hierarchy in Spring JDBC exists, is because SQLException is the only exception for all types of problems. In order to allow more selective catch-clauses, a new hierarchy was created, mirroring the different kinds of errors that would typically occur in the JDBC world. By contrast, JmsException is the base class for a mirrored hierarchy of the rich (but checked) JMSException hierarchy. In the LDAP world, there is a rich (but checked) hierarchy based on NamingException. Wouldn't the JMS approach suit us better than the JDBC approach?

[ Permlink | « Hide ]

Ulrik Sandberg added a comment - 18/Dec/06 03:22 PM

Adding a view of the NamingException hierarchy.

[ Permlink | « Hide ]

Ulrik Sandberg added a comment - 12/Jan/07 10:36 AM

Instead mirrored the NamingException hierarchy with a matching unchecked hierarchy, and now simply translating to those, much like Spring JMS.