RE: [Springframework-developer] Private bean constructors

[Alef A. <al...@jt...>]

> I think we should. The reason I think so is that realistically, the
> beanfactory and appcontext are plumbing which is meant to hook stuff
up
> together. In this scenatio, I think the fact that a constructor is
> private and normal java code should not be able to use it is sometimes
> irrelevant. Some people may even consider it cleaner not to expose
> constructors, so that normal code can't instantiate the object, but a
> beanfactory/appcontext can. In this respect, I think the deployer
knows
> best, although we should probably warn agaisnt the practice.

+1