| Hi,
JSR-330 would be a very valuable addition to the JDK, although it's just about annotations it would be good to have them standardized and shipped with the JDK. I've been using Spring for a couple of years and in TMF Xtext we use Guice for some month with great success and much fun. Dependency Injection (like OSGi) should be part of the language / JDK.
my 2 cents, Sven
On May 27, 2009, at 7:27 PM, Mike Milinkovich wrote: Boris, I got a similar note from Bob Lee J It would be great to hear the opinion of others on how we should vote. Having the advice of the Architecture Council would be very helpful data point, I am sure. But in the end Wayne and I are going to make the final decision. Mike Milinkovich Office: +1.613.224.9461 x228 Mobile: +1.613.220.3223 Mike, Architecture Council,
The Eclipse Foundation is a member of the JCP SE/EE Executive Committee, which "is responsible for approving the passage of specifications through key points of the JCP" (http://jcp.org/en/participation/committee).
Mike, you are the Eclipse Foundation's representative on that committee. On what basis do you make voting decisions? Would it make sense to involve the AC on this in some way?
The concrete background of this is that I have been asked by Bob Lee, one of the proposed spec leads for JSR-330 "Dependency Injection for Java", that the Eclipse Foundation vote "yes" on this JSR which is up for "JSR review", i.e. whether it gets approval for development in the JCP. Personally, I think that the proposal looks good, and that it would be in Eclipse's interest to support the JSR, but it doesn't feel right that I just send an email to you without involving others from the Eclipse community.
Questions? Comments?
Boris _______________________________________________ eclipse.org-architecture-council mailing list eclipse.org-architecture-council@xxxxxxxxxxxhttps://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-councilIMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.
|
