I also reduces clutter in your page/component classes. I was already using
this for DAOs because I have one DAO per entity type. Some pages would have
4 or 5 @Injects for DOAs. Now they have one.
Secondly it defines the public API. If you use T5 you do not have access to
private services.
Lastly since it also creates services there is really no development
overhead in using it. Instead of
binder.bind(Foo.class,FooImpl.class)
you have
@Binder(implementation=FooImpl.class)
public Foo foo();
I'm guessing there is some overhead to this but there must be some overhead
in @Inject also. I suspect in most cases is it does not make much difference
one way or the other, but since you can still use services with @Inject
so you can always do this
@Inject Foo foo;
for ( i=0; i < 1000000; i++) {
foo.method()
}
instead of
for ( i=0; i < 1000000; i++) {
t5.foo().method()
}
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Library-binder-and-IDE-helper-tp5715397p5715449.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
