I'll give it a shot. Basically, the model-view-controller pattern separates a model from its views (and, optionally, controllers to change the model). A simple example could be some kind of data (e.g. financial data), and several vies showing this data, e.g. as a chart, a graph, etc. You might also be able to modify the data in the chart, so this would also act as a controller.
In a JSP-based web application, MVC could be implemented this way: A JavaBean would contain the model, consisting of some data and business logic (e.g. a stock portfolio). One ore more
JSP pages can use the JavaBean to display this model, or aspects of the model. They would also (possibly) act as controllers to modify the data in the model, e.g. by allowing the user to add a new stock to the portfolio.
I hope this makes sense. :-)
-Mirko