Hi guys,
I've been thinking about the way in which wicket is an MVC framework and
whether people use it according to the MVC pattern.
Wikipedia has this to say:
Model
The domain-specific representation of the information on which the
application operates. Domain logic adds meaning to raw data (e.g.,
calculating if today is the user's birthday, or the totals, taxes, and
shipping charges for shopping cart items).
Many applications use a persistent storage mechanism (such as a
database) to store data. MVC does not specifically mention the data access
layer because it is understood to be underneath or encapsulated by the
Model.
View
Renders the model into a form suitable for interaction, typically a user
interface element. Multiple views can exist for a single model for different
purposes.
Controller
Processes and responds to events, typically user actions, and may invoke
changes on the model.
I'm interested in whether people are using the model to encapsulate service
calls. In the wicket documentation I frequently see services in the page
retrieving dtos and passing the dto to a component as a model. This seems
to be in conflict with the description of a model in the mvc pattern.
Wicket is supposed to be an mvc framework, so why do the examples put
services/daos in the pages?
What patterns are folks using for their wicket apps?
--
View this message in context:
http://www.nabble.com/patterns-for-web-ui-apps.--mvc-models-tp18214140p18214140.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
