[cdi-dev] [JBoss JIRA] (CDI-170) Either ditch or fix @New

[ https://issues.jboss.org/browse/CDI-170?page=com.atlassian.jira.plugin.sy... ] Mike Brock commented on CDI-170: -------------------------------- The elimination of {{@New}} is actually quite high on my list of CDI features I'd eliminate if I had a magic wand. It's not as high as my desire to remove narrower-scope injection. But it's pretty high. To me, {{@New}} is something you'd basically never use in a new system built on CDI. At least, I'd never use it. I'd jump through hoops not to. But you _may_ find it necessary to use in a system you are maintaining, when you're stuck with a bad design decision made by someone else that you simply can't change. It stretches the limits of my imagination to come up with a scenario where this may be, but I'll just assume it does. CDI is a declarative programming model. And I think a desirable characteristic of any declarative programming model, is that the meaning of declarative constructs be as plain and straight forward is as reasonably possible. I believe {{@New}} directly undermines this goal. It creates an information asymmetry between what a bean declares its scope to be, and what the scope may actually be at the call site. To me, this is a particularly offensive characteristic. But I'm not count on winning anyone over on my desire to nix/deprecate {{@New}}. I merely wanted to voice my opinion on the matter. There are, in fact, other hills I'd feel more morally righteous about dying on than this one. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira