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.
jürgen höller [werk3AT] wrote:
>Do we want to support this?
>
>http://opensource.atlassian.com/projects/spring/browse/SPR-174
>
>It's easy to do, but definitely not a best practice.
>
>Juergen
>
>
>DI Jürgen Höller
>Senior System Architect
>______________________________________
>
>werk3ATS - division systementwicklung
>werk3AT informations- und mediensysteme
>
>europaplatz 4
>A - 4020 linz
>
>t. +43 (0) 732 71 65 29 502
>f. +43 (0) 732 71 65 29 3
>mailto:jue...@we...
>http://www.werk3at.com
>______________________________________
>werk3ATS - WIR ENTWICKELN ERFOLG
>
>
|
