A couple of TODOs in the attributes code.

[Rod Widdowson]

I have been doing some housework and cleaning some TODOs.

There are a three left, all are in the LDAP and/or RDBMS data connectors so
I'm leery of just going in there.

The first is about attribute value mapping in LDAP.  I think this ties back
into the RDBMS mapping that Scot and I are looking at.  However it refers to
new function "Do we want to do data mapping as we do for RDBMS?", and I
think right now we can say "no".

The next is asks whether we 'use queryUsesStoredProcedure', and again I
think that the answer is 'no'?

The last TODO is about moving hard wired defaults from the LDAP parsers into
the bean definitions.   This is not just a simple matter of adding some
constants into beans because firstly there are non-custom-spring ways of
setting up the beans, and secondly in many cases the beans are not ours -
they belong to ldaptive.

I'm thinking that the best solution is to have subclasses of the ldaptive
beans with the defaults in place.  But, I'm not 100% convinced:
  - It could be said that we are moving the defaults from one hard to find
location to another.
  - And if people really want the fine control, then they will not be using
our custom schema, they'll use Spring.

Thoughts?