This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
Only one servlet for whole project, and that is the controller
Difference between *action java classes* and *model java classes* are:
action java classes are having (or using) web objects such as request, response, session etc, the purpose of these classes is, getting useful data from these web objects and calling methods defined model java classes...
model java classes are having actual business logic methods, they are not having any web objects so we can write Junit easily.
Please let me know, something is new or not.... good or not...
Thanks a lot.
[ December 25, 2005: Message edited by: rathi ji ]
Originally posted by rathi ji: But why they don't include Action in the name. It also serves important purpose...
Because action is not really qualify for this. The role of action is just to help controller to make navigation/flow decision. And it would be at minimum if we implement MVC without Front Controller Pattern and Command Pattern. And we generally have alot more things other then Model, View, and Controller, so what do you think the initials of all should have been there in MVC. like
MVCA/CH - (Model, View, Controller, Action/Command, Helper), just a thought. [ December 27, 2005: Message edited by: Adeel Ansari ]