I feel like I remember seeing this conversation before but can't find it in my mail search.
Just noticing that if we throw a RuntimeException from an @Init method in a composite-scoped component ... then the instance gets used anyway even though it may have failed to initialize. Was thinking it would be a useful service for the container to provide to discard the instance, under the assumption that the next time the service is invoked, we'll retry the instance creation, since maybe later the @Init will complete successfully? Don't see anything in a very quick scan of the specs but I didn't look thoroughly. Any thoughts on this? Thanks, Scott
