Selective Parsing?

[Cantor, Scott]

On 3/11/14, 12:59 PM, "Rod Widdowson" <rdw at steadingsoftware.com> wrote:

>I'm not sure that I completely understand this, probably because "context"
>is a term which is overloaded everywhere, but specifically in this case.

What I was suggesting was, when we create a context for a Service
abstraction, we could create a context with some kind of bean defined as a
signalling tool, and then create a child context for the actual "real"
beans. Then the parsers would do getBean or whatever on the app context,
which would delegate to the parent, and that's your side channel.

>However this is probably all irrelevant.

Probably.

>Again, nothing needs to be decided at this immediately, but my favoured
>approach is to use lazy initialization, particularly on the metadata
>providers.

I'm probably ok with that, particularly if we end up in a place where it's
only done for legacy configurations. But I'm not sure we'll end up there
because of the overlap between metadata verification and the security part.

One way out might be to provide metadata and security bits out of one
service interface.

-- Scott