For the singleton: 80% of the time I want "unscoped" aka dependent/instance/prototype/ injection scope. Apparently I am not the only one as this is default in JSR-330 and JSR-299.
When DI was not that wide spread I can understand that any choice of default scope is fair ground. But now we had a lot of time to see what most people use 80% and what 20% of the time. And it looks like 80% of the time it is the unscoped. There are plenty of good reason for this as Brian pointed out. I want defaults to cover what I do 80% of the time. Can I assume you use singleton 80% of the time? For error reporting: All I'd you to understand is that error reporting should not be an after thought. It should be at the very heart of the framework. Guice even exposes API methods for this. I don't consider the 1 API method as green and Guice's 20+ as red. If any that is a limitation not an advantage. If you're offended by any of this...then hm... For your columns in the comparison: Guice can do c'tor injection without requiring annotation with to toConstructor binding (so it is annotations or fluent interface and not requires annotation). Cheers Alen On Apr 8, 5:35 pm, Jan Bernitt <[email protected]> wrote: > If you seriously want help on this and not just bash on Silk than you > should use Silk grouphttps://groups.google.com/group/silk-disince this > is purely Silk related. Of cause it is of importance how you defined the > RootBundle class. > > There actually is such a category. But no row for "overall feeling of > reporting quality" since this obviously is subjective. > Anyhow I have no problem to agree that guice has a very good reporting > and silk is not there yet. This has to evolve through the usage. > But it is good enough to see what the problem is - the below stack is > informative enough to get an idea. > > This singleton topic is funny. Where are the arguments ? Are you sure > you don't confuse JVM singletons with container singletons ? Are you > sure you do not talk about some kind of special use problems like for > example GC related issues in application of very extreme characteristics > when it comes to this ? > > Jan > > On 08.04.2013 16:57, Alen Vrečko wrote: > > > > > > > > > I tried to use it. It doesn't work. I get > > > Exception in thread "main" java.lang.RuntimeException: > > java.lang.NoSuchMethodException: playground.Silk$RootBundle.<init>() > > at se.jbee.inject.bootstrap.Inspect.noArgsConstructor(Inspect.java: > > 242) > > .... > > > I have > > > class Foo > > class Bar(Foo foo) > > > Injector injector = Bootstrap.injector(RootBundle.class); > > Dependency<Bar> dependency = Dependency.dependency(Bar.class); > > Bar instance = injector.resolve(dependency); > > > You should add another category: error reporting. You can put both > > Silk and Spring in red and Guice in green. I tried to follow your > > guide but I get the mentioned stack-trace. > > > I cannot help myself but to say the the usage of Singleton as the > > default scope is archaic. In my book it qualifies for a QUADRUPLE > > FACEPALM badge!!! > > > Cheers > > Alen > > > On Apr 4, 9:07 am, Jan Bernitt <[email protected]> wrote: > >> Hi, > > >> I made a comparisonhttp://www.silkdi.com/help/comparison.htmlpage > >> comparing my DI tool to other frameworks and guice is one of them. > > >> Please let me know if I got something wrong (in the guice column) or you > >> have additional or yet missing information I could add to make it more > >> complete. > >> Any other feedback is of cause also welcome. > > >> Jan -- You received this message because you are subscribed to the Google Groups "google-guice" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-guice?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
