Simple MVC - Displaying a Customer
What you have here is not MVC. It's DataVC, this results in some minor and major design problems.
Unwrapping data in the Controller
That's the first really bad idea here. You're trying to hide the way Data is structured from the View, based on the assumption that the Model is the Data.
That's not the case. Just pass your Customer-instance to the View for display. The view knows what it needs from the Customer to display it properly.
The Controller doesn't.
Model != POJO
The Model in an MVC application is not the &quot;Domain Model&quot;. It's instead the Layer to provide instances of classes modelling that Domain Model (in your case Customers).
Instead of having the Controller receiving a Customer from the calling code (which is unsustainable in larger applications), you should make the Controller ask the Model for customers depending on user-input.
More nitpicks

Your package-declaration should hint at a domain you own.
Making the Customer's field accessible through getters on the Controller is a dumb idea. The Controller doesn't actually have to know about the internals of Customers and shouldn't be asked about them