I think you're infected by the deadly OO blather
The best, and currently most often overlooked, principle of software engineering is KISS
(not to be confused with KISS
Classes should be well focused, but don't throw out the baby with the bath water. All your GUI component action listeners should be in your GUI class, though they may in fact just be skeletons that call a method in some other class to do the real work.
The OO "Model" in the case of FBN is that class/classes that deals with the Oracle/relational-database like "data model," the "View" of which will be created by your GUI. The Model shouldn't be concerned with- or particularly even aware of- the View, and vice-versa.
To realize this isolation, you of course need some "Controller" glue in-between, which is where the real work is done on behalf of your GUI(when you click on your Search button, for example).
In your Model, you'll do database-oriented "business logic" stuff like checking to see if there are enough seats available for fulfill the client's request. If not, you throw an OhHellException, which will be caught, and dealt with appropriately, by your Controller.