My intuition for the "model" is "that which is serialized to disk" (or,
more generally: "to persistent storage"). This means that such a class
does not contain any business logic but only has getters and/or setters.
In reality (and in many nontrivial projects) the distinction is not as
strict, so your "model" class may very well have methods that go beyond
getting/setting properties and you may in fact have instances of "model"
classes that live (at least temporarily) outside the "model" domain.
Robert
Am 25.05.2010 12:14, schrieb Fabio Perfetti:
so? what is the model? the beans?
public class Employee{
private String name;
private String surname;
public setter/getter ...
}
2010/5/25 Antonio Petrelli<antonio.petre...@gmail.com>
2010/5/25 Fabio Perfetti<perfabi...@gmail.com>:
I am wondering if the actions belongs to the model layer or to the
controller layer.
Actions are by definition part of the controller.
All the example on the web are simple!
Anyone can explain me? (with an example please)
No example but a simple argument: the model exists *without* the need
of any controller part, especially actions.
Antonio
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org
