This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
jsr 330 and jsr 299 is good...Eclipse e4 has projects to do this. Why NetBeans not? I think we need the @Inject and @Resource related Annotation at the begining step to simplify the development... Such as: @Logger Log log a specified Inject to inject a logger in class, some like the seam Log. @Resource ImageIcon edit; To inject a binary image resource in "edit" from moudle resource folder( eg "METAINF/resoures/", let NetBeans find related file and file mimetype automatically, like in the GNOME desktop file, we need not specify the extension of the icon image) and platform resource folder(if can not found in module resource),it should apply the Configuration on Conservation principal,and It also can accpet a value to specify the location througth URL, such as @Resource("nbresource:/res/edit.png")... @Inject Messages messgaes The ResourceBundle files are also need to apply the Inject or Resource(specify the file) annotation, and add a simple way to use it, like the seam FacesMessages class. @Inject @Current Project project To get a current project instance...thus can remove tedious Lookup codes. ....and etc. This is just of my dream. If NetBeans has some plan like this, I think it needs a further discussion.
I was thinking about using the JSR 330 myself. The question however is: how? It definitely needs more discussion. If you have some links about the way e4 wants to use it, please share them. However I don't believe issuezilla and P3 bug is appropriate for a discussion like that. Closing the bug as invalid. Not as "invalid" idea, but invalid in "not a bug" meaning.
it is an new requirement...
There are much resources about Eclipse and JSR 330...E4 introduces the new CSS/XWT/DI(JSR 330)... Here I list some of them... http://www.slideshare.net/LarsVogel/eclipse-e4-tutorial-eclipsecon-2010-3587897 http://www.slideshare.net/LarsVogel/eclipse-e4-overview http://eclipse.dzone.com/news/eclipse-4-goes-extra-mile U can use google to get more...
I am not the guru of NetBeans or JSR330...so I think NetBeans should make such a plan of this topic, and create a wiki page to discuss with other NetBeans experts.
I am sorry , I am a none English guy, maybe my expression is not clear as u expected.
Created attachment 102891 [details] code sample for this...
I am trying to get some ideas on nbdev@ (see http://netbeans.org/projects/www/lists/nbdev/archive/2010-11/message/42), but so far no luck. I guess this issue ends up won'tfix.
More info: http://hwellmann.blogspot.com/2010/11/cdi-major-risk-factor-in-java-ee-6.html - a.k.a weld is not an option now (in spite of excuses in http://in.relation.to/Bloggers/WeldsPerformance).
I have nothing against JSR-330, but current ideas are so vague that I can't implement anything. So this issue is either invalid (too vague) or won'fix (nobody to work on it). Of course, if you can donate patch to make your ideas more concrete, feel free to reopen.