[MGNLLDAP-45] Use NamingEnumeration.hasMore() and next() systematically Created: 01/Nov/10 Updated: 30/Nov/10 Resolved: 01/Nov/10 |
|
| Status: | Closed |
| Project: | LDAP Connector |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.4.1 |
| Type: | Task | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Magnolia International |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Template: |
|
||||
| Acceptance criteria: |
Empty
|
||||
| Task DoR: |
Empty
|
||||
| Description |
|
Some of the reasoning is explained or linked to in MGNLLDAP-39. Using the Enumeration methods (hasMoreElements(), nextElement()) hides any exception; while this satisfies many scenarios, by simplifying the problem, it doesn't solve. Using the specific NamingEnumeration hasMore() and nextElement() methods make problems more prominent, thus reducing the probability of side-effects or inconsistent results. http://download.oracle.com/javase/jndi/tutorial/ldap/referral/jndi.html |