Hi,
As you are using the MVC model, I understand that changes to the model would result in property change events being fired to the controller, which would then update the view. Your class that contains all the properties is part of the model.
Why create a method that takes in your holder class (model), on the controller ??
Why not have the controller as a property change listener on the model ? This way the controller will only need to implement the propertyChanged(PropertyChangeEvent e) method. The model would then fire off property change events, where the PropertyChangeEvent would contain the old and new values.
Hope this helps.