that's true for diagram 9-8 but in diagram 9-7 there is not dependency injection arrow. I would not introduce depandency injection in my sequence diagram. I think dependancy injection is an implementation detail and a base of ejb 3. In the class diagram 9-3 he introduced a package App Framework. For me this technical package would be the right place for dependency injection.
The question remains, how can i represent a call in a sequence diagram assuming that i´m using dependency injection. I´m not aware of any arrow with dependency injection on it.
Can anyone point to any examples?
The question remains, how can i represent a call in a sequence diagram assuming that i´m using dependency injection
I don't see your problem here. The fact of the matter is, you're not using dependency injection, the container is. Let's assume BeanA is invoking some method on BeanB. How BeanA got a reference to BeanB is completely irrelevant in the context of the method call.
I´m not aware of any arrow with dependency injection on it.
That's because you model structure in class, not sequence, diagrams.
I agree with you, in the sequence diagram it´s a call like another. But in my assignment i have two ways of accessing the session beans, with a service locator and other with dependency injection.
And i have the problem of distinguish the two ways in the diagrams (class or sequence diagrams)
I´ve found i guy that represent the dependency injection in the class diagram with a stereotype <<injected>> in the attribute that represent the session bean that will be invoked.