ldap data conn config convo ?
Cantor, Scott
cantor.2 at osu.edu
Sun Mar 17 18:07:45 EDT 2013
On 3/17/13 6:01 PM, "Tom Zeller" <tzeller at dragonacea.biz> wrote:
>I would like to get all of the issues on the table, but I do not
>remember exactly what was said. External config files ? The spring
>p:namespace ?
The underlying requirement was being able to get coverage of all the
advanced options in ldaptive without having to create custom XML for it. I
heard agreement that we wanted to make it possible, but use native Spring
XML if possible.
We talked about whether we could embed the native XML inside the custom
XML and you were concerned about the recursion there. So I think the
compromise was figuring out a way to define beans separately and then
reference them within the custom XML? That was as much detail as I thought
we reached at the time. I didn't know if that meant separate files,
separate elements within the resolver schema, or something else.
I had noted that the p:namespace thing seems like a reasonable shorthand
that's not really that ugly for deployers in at least some cases, but that
was more a general point that I thnk we would be ok with native XML if
it's compact enough. I like the flexibility Spring's "anything goes"
syntax has, but I know it's not practical for most people.
-- Scott
More information about the dev
mailing list