Similar to Spring, Pop Framework (or shortly, Pop) implements IoC, Dependency Injection, AOP.
The difference is that the Pop implements those in Java syntax, instead of XML. And moreover,
Pop uses beans in MVC.
With Pop, you can define a bean in Java syntax and then reference it directly. You needn't to
learn the XML syntax of defining and referencing a bean, needn't to learn the syntax of using
AOP, and etc.
Pop is nothing but a set of packages of Java classes. So it is strong-typed and objected-oriented,
and it's very easy for you to learn and use it. Pop provides a more natural way for a programmer
to define and reference a bean, and to use AOP and MVC.
MVC mechanism in Pop is totally different with that in other frameworks such as Spring and
Structs. In Pop, MVC is based on bean mechanism. In Spring, for example, MVC and Bean are
separated and independent from each other. That's OK in Spring for you to use the MVC without
using beans. In Pop, however, the model of a web page (such as a JSP or a servlet) must be a bean.
The JSP/servlet itself is treated as a view of the bean. The bean provides the data for the view,
the view is responsible for rendering the data.
So in Pop MVC, bean (or say model) is the core of any web pages. The only task of a web page (or
say view) is to render its model/bean to client side.
For more details, please refer to http://www.popframework.net