SetID

[Cantor, Scott]

On 8/5/14, 6:59 AM, "Rod Widdowson" <rdw at steadingsoftware.com> wrote:
>
>I'm not sure what you mean by implicit.  I do think that we need to look
>at
>the explicit calls and make sure that their inputs are guaranteed
>non-null.
>The implicit calls should all be deal with by the bean post-processor (see
>below).  Again, I'll take a UI to check that (manually).  I'll enter a
>case
>to track this.

What I meant by implicit is calling it in the constructor.

In particular, it doesn't help for logging if the ID is a random value
anyway.

>I don't see that making the code more complex serves anything and I'm not
>sure that distinguishing custom-parsed beans from standard beans gains us
>anything.  But again I missed the last meeting.

The reason I think it makes a difference is that with things happening
"under the covers" in the Spring parsers, it's much harder to see what
objects are there and what their properties are. But with the native
files, you generally can see everything, so anything that's erroring out
has a bean ID you can go after. Even if an inner bean is failing, it fails
the outer bean's creation.

-- Scott