In simple terms, Inversion of Control allows developers to save effort and time by
allowing some other software to take care of different routine things and provide
them services whenever needed.
However, to use the benefits of Inversion of Control in an application, one might
need to learn and use an additional framework like Spring. Not in Tapestry though.
Tapestry has an Inversion of Control subsystem of its own, and quite a good one.
As a result, Tapestry applications contain very little Java code. All you need to
write is business logic while all the infrastructure issues are handled automatically.
Aditionally, the Tapestry 5 IoC container additionally provides an opportunity
to implement and enforce some of the best design patterns, again, with absolute
minimum code serving this purpose.
Spring framework is very popular, and working on a large-scale enterprise
application, we often need to make use of some sort of back end, implemented in
Spring. Thankfully, Tapestry has a special subsystem for integration with Spring.
Using this subsystem in my work, I had an impression that it is easier to use Spring
beans in Tapestry than in Spring itself.
More or less the same can be said about integration with another very popular
framework, Hibernate.
Pages:
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33