Don, > JSR 330 is not the magic bullet here.
Agreed, but I would have to say it would be foolish not to support it. As companies perform internal tech evaluations, people will eventually realize "standard" DI injection is not supported: "Oh, our company has to learn XWork DI? What the heck is XWork?" Well, that could be seen as a negative and affect adoption. A FUTURE scenario, but one likely to occur one day. I don't care what DI container runs JSR-330, but it should be the job of Struts 2 to allow *swappable* implementations through a Bridge adapter. Will our users have the choice of Apache's Open Web Beans [1]? I hope so. Likewise, Commons Validator 2.0 will be a JSR-303 Bean Validation implementation. Same lesson to be learned here. [1] http://incubator.apache.org/openwebbeans/ Paul --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
