Multiple Jpanel with buttons in one Jframe on MVC, how do I get the actionlistener in my controler ?

The problem is you are calling getAjouter() on CreerRechercherAbsence JFrame instance in your ActionListener where as you'd want to be calling getAjouter() on RechercherAbsenceP3 JPanel instance.

My solution:

Convert your ActionListener class GestionAbsenceEmployes to accept RechercherAbsenceP3 as the parameter so we can call getAjouter() on its instance like so:

class GestionAbsenceEmployes implements ActionListener { private AbsenceEmploye modele; private RechercherAbsenceP3 vue; public GestionAbsenceEmployes(RechercherAbsenceP3 uneVue) { this.modele = new AbsenceEmploye(); vue = uneVue; } public AbsenceEmploye getModele() { return modele; } @Override public void actionPerformed(ActionEvent event) { Object source = event.getSource(); if (source == vue.getAjouter()) { } } } 

you would than do:

 aControleur = new GestionAbsenceEmployes(absenceP3); 

but in order for the above statement to function you must change this:

private JPanel absenceP1, absenceP2,absenceP3; 

in CreerRechercherAbsence class to this:

private JPanel absenceP1, absenceP2; private RechercherAbsenceP3 absenceP3; 

because you extend JPanel to add functionality hence the RechercherAbsenceP3 but by declaring it as JPanel you down cast it, thus it does not have access to the methods of extended JPanel RechercherAbsenceP3 and only those of default JPanel.

Some other suggestions:

• Do not extend JFrame class unnecessarily

• No need for getContentPane.add(..) as add(..) has been diverted to contentPane

• Be sure to create and manipulate Swing components on Event Dispatch Thread

Not sure whether the following approach will be considered MVC, or whether it will result in good marks on your assignment.

My "problem" with your current approach is that the reusability is limited to the model, and that it looks difficult to write a decent test case for this code, unless you are prepared to write tests which include the whole view.

When I need to write a Swing application, it seems that I only end up with 2 classes: a model class defining the data and the operations available on that data, and the view class. The view class functions both as view as well as controller. When I have a button as in your example, I would attach an ActionListener to it (or use an Action) which just retrieves the necessary information from the view without any logic. It passes all that information directly to the model side where all the logic is located.

The two main benefits I see in this approach:

• I can re-design my view without any problems. If I decide to remove a JButton and provide the user with another mechanism for that same operation, all my changes are limited to the view. I have no dependency on UI elements except in my view class. I see all the "information gathering and passing it to the model" directly in my view class, and due to the implementation of that view this will not affect other classes. Compare that with your code where you have a source == vue.getAjouter() check in a class outside your view.
• I can test the model and all its logic without needing my actual view. So I can skip the whole "firing up a Swing UI" in a unit test and still test all my logic. If I want to test the UI (for example to test whether a certain button is disabled when a field is left blank) I can test this separately in an integration test (as having a UI tends to slow down your tests).

What I found a very interesting article in this regard is The humble dialog box

Here is how I would do it. Make GestionAbsenceEmployes a non-static inner class of CreerRechercherAbsence

public class CreerRechercherAbsence extends JFrame { private GestionAbsenceEmployes aControleur; private JPanel absenceP1, absenceP2; private RechercherAbsenceP3 absenceP3; // code omitted public CreerRechercherAbsence() { super("Gestionnaire des employés absents"); try { jbInit(); } catch (Exception ex) { ex.printStackTrace(); } aControleur = new GestionAbsenceEmployes(); } // code omitted class GestionAbsenceEmployes implements ActionListener{ private AbsenceEmploye modele; public GestionAbsenceEmployes() { this.modele = new AbsenceEmploye(); } public AbsenceEmploye getModele() { return modele; } @Override public void actionPerformed(ActionEvent event) { Object source = event.getSource(); if(source == absenceP3.getAjouter()) { } } } 

No need to pass this to the constructor and the controller does not need a reference to vue. You get all that for free by making this an inner class. Your controller can access all the member variables of the view. So you can now access the absenseP3 panel with the getAjouter() method.

See http://docs.oracle.com/javase/tutorial/java/javaOO/nested.html for more information on when it makes sense to use inner classes.