On 21-Apr-09, at 07:02 , manuel aldana wrote:
Christian Edward Gruber wrote:
On 20-Apr-09, at 19:39 , Thiago H. de Paula Figueiredo wrote:
Now I get it. Thanks Christian!
All you said, to me, is one more reason to not inject services in
domain objects . . . :)
Yeah - that's such an anti-
Thiago H. de Paula Figueiredo wrote:
If applicable I try to inject services to domain-objects to add
pluggable behaviour to them (so I don't end up with an anemic domain
model).
I disagree with adding services to domain objects. But please let's
not start a discussion about it. This is not
Christian Edward Gruber wrote:
On 20-Apr-09, at 19:39 , Thiago H. de Paula Figueiredo wrote:
I think he means value objects or domain models. You can't usefully
have the container create an instance of Movie because movie is a
data-carrying node. It's a bit like having the IoC container crea
On 20-Apr-09, at 19:39 , Thiago H. de Paula Figueiredo wrote:
I think he means value objects or domain models. You can't
usefully have the container create an instance of Movie because
movie is a data-carrying node. It's a bit like having the IoC
container create any random Map you might
Em Mon, 20 Apr 2009 20:26:17 -0300, Christian Edward Gruber
escreveu:
I think he means value objects or domain models. You can't usefully
have the container create an instance of Movie because movie is a data-
carrying node. It's a bit like having the IoC container create any
random Map
I think he means value objects or domain models. You can't usefully
have the container create an instance of Movie because movie is a data-
carrying node. It's a bit like having the IoC container create any
random Map you might need. If it's a named Map that is a central
store for somethi
Em Mon, 20 Apr 2009 19:05:24 -0300, manuel aldana escreveu:
Your convention makes sense, but what do you do with objects which are
usually created directly by other code and not by tapestry, thus
constructor injection won't be the best solution?
If it's possible, I add the object as a Tape
Thiago H. de Paula Figueiredo schrieb:
Em Mon, 20 Apr 2009 16:38:51 -0300, manuel aldana
escreveu:
When does tapestry-ioc inject stuff to object (@Inject annotation)? I
guess it is straight after finishing the constructor...
Is it possible to have the injection already available after the c
Em Mon, 20 Apr 2009 16:38:51 -0300, manuel aldana escreveu:
When does tapestry-ioc inject stuff to object (@Inject annotation)? I
guess it is straight after finishing the constructor...
Is it possible to have the injection already available after the call of
super() inside the constructor?
When does tapestry-ioc inject stuff to object (@Inject annotation)? I
guess it is straight after finishing the constructor...
Is it possible to have the injection already available after the call of
super() inside the constructor? This way the injection would be
available already inside the re
10 matches
Mail list logo
