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

Cantor, Scott cantor.2 at osu.edu
Mon Feb 10 14:47:12 EST 2014


On 2/10/14, 2:13 PM, "Cantor, Scott" <cantor.2 at osu.edu> wrote:

>The problem with the Spring code in the resolver that's turning validation
>off is that the schemas we have don't allow for the <beans> element yet. I
>can add that, but I'd need to know what we plan to actually support in
>terms of combining that syntax with the custom schema.

Actually I'm wrong, the reason validation wasn't working on the "inner"
parse Rod's doing to handle the embedded <bean> element is that Spring
still needs an xsi:schemaLocation to be declared in that XML for it to
find its own beans schema. writeNode() will to namespace fix up, but it
won't pull in schemaLocation from the parent context, even if we added the
Spring line to it.

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.

-- Scott






More information about the dev mailing list