Hi,

what do people think about supporting field injection in Aries blueprint?

It's not in the OSGi blueprint spec, but a lot of other JEE specs support field injection (Servlet, EJB3, JPA ...), so developers might assume the convenience of not having to write pointless getters and setters.

An Aries specific extension to blueprint could then allow field injection per bean or per blueprint module controlled via a custom namespace attribute. At runtime this would allow the Blueprint container to inject a property directly into a field (regardless of visibility). However, this alternative approach would only be used if a setter is not available (so setters would always take precedence).

If there no violent objections, Ozzy and I will look into implementing this ;)

Regards,

Valentin

Reply via email to