Schema support for Spring <beans> in LDAP/RDBMS config

[Cantor, Scott]

On 2/10/14, 2:47 PM, "Cantor, Scott" <cantor.2 at osu.edu> wrote:
>
>What I don't understand is how this works at all given the parent parse.
>That step should fail to validate because <beans> shouldn't be legal in
>our V2 elements. I'm very confused by that.

And that's less confusing once I realized the tests turn off validation in
the Spring reader.

We have to make some schema changes if we're going to allow <beans>
inline, and I'm not sure how intelligent the code is about handling errors
at this point.

The main sticking point, assuming we wanted to make <beans> an alternative
to any legacy content, is that there are various XML attributes on the
DataConnector element that are required, like ldapUrl.

I assume if any required properties aren't set that the DataConnector
would just fail to init, so perhaps it's safe to just make them all
optional, but I don't know if that's true.

It's going to be more complex to come up with a schema if we have to allow
mix and match of old elements and <beans>.

-- Scott