Dependency Bijection

[ranophoenix]

1.3. POJO Services via Dependency Bijection

Seam is a “lightweight framework” because it promotes the use of POJO (plain old Java objects) as service components. There is no framework interfaces or abstract classes to “hook” components into the application. The question, of course, is how do those POJOs interact with each other to form an application? How do they interact with container services (e.g., the database persistence service)?

Seam wires POJO components together using a popular design pattern known as “dependency injection” (DI). Under this pattern, the Seam framework manages the lifecyle of all the components. When a component needs to use another (e.g., the UI event handler component needs the user input data encapsulated in an entity component), it declares this dependency to Seam using annotations. Seam determines where to get this dependent component based on the application’s current state and “injects” it into the asking component.

Expanding on the dependency injection concept, a Seam component A can also create another component B and “outjects” the created component B back to Seam for other components, such as C, to use later.

This type of bi-directional dependency management is widely used in even the simplest Seam web applications (e.g., the hello world example in Chapter 2). In Seam terms, we call this “dependency bijection”.

Será que os outros frameworks irão implementar este novo design pattern utilizado pelo Seam!?

• editado pelo moderador para arrumar a quebra de linha

[leonardom]

Se eu não estou enganado o VRaptor já faz algo assim! Vc pode criar um objeto em um interceptor e usá-lo depois.

[ranophoenix]

Tem um exemplo de como funciona aqui:

http://docs.jboss.com/books/seam/ch02.html