wicket-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Igor Vaynberg" <igor.vaynb...@gmail.com>
Subject Re: patterns for web ui apps. mvc models
Date Tue, 01 Jul 2008 15:37:58 GMT
if it doesnt have patterns how will the enterprise architect be able
to model it????


On Tue, Jul 1, 2008 at 8:23 AM, Thomas M├Ąder <tomlist0408@gmail.com> wrote:
> Wicket is a framework to write (mostly) statefulweb pages. Unlike other web
> frameworks it does not impose a particular way to structure the application
> logic beyond that. Think of it like, say, the QT widget set. It's a way to
> display information and to be notified of user interactions.
> Thomas
> PS: when did the notion start that design pattens had an intrinsic value?
> "Now new and improved with more patterns!" Patterns are ways to structure
> (sorry for the shouting, pet peeve)
> On Tue, Jul 1, 2008 at 2:07 PM, marco m <marco.montgomery@gmail.com> wrote:
>> 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: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org

To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org

View raw message