I'm not sure I understand what you're after, maybe something like this:

T1A t=new T1A();
tf1.addActionListener(t);
tf2.addActionListener(t);
jButton1.addActionListener(t);
jComboBox1.addActionListener(t);
//etc.......

class T1A implements ActionListener {
 public void actionPerformed(ActionEvent e) {
   Object o=e.getSource();
   if ( o==tf1 ){
      //do something....
   }
   else if ( o==tf2 ){
      //do something else....
   }
   else if ( o==jButton1){
      //do something else....
   }
  //etc..
 }
}

You don't even need any new classes.
Just have the class that you are writing (the one that contains
all the buttons, texts, etc.) implement ActionListener.
Then for each button:
   button.addActionListener(this);
and create an actionPerformed() method in your class
that checks the source:

public void actionPerformed(ActionEvent e) {
    Object obj = e.getSource();
    if ( obj == button ) {
         // do something
    }
   else if ( obj == button2 ) {
       // etc.
   }
}

man4*.* schrieb:

Depends. If you've got 10 completely different tasks then yes (forget
about if-else/switch-constructs to create whole-world-listeners).

In many cases you can reuse classes:

class TextSetterAction implements ActionListener {
    private JTextComponent tc1;
    private JTextComponent tc2;

    public TextSetterAction( JTextComponent tc1, JTextComponent tc2 ) {
        this.tc1 = tc1;
        this.tc2 = tc2;
    }

    public void actionPerformed( ActionEvent e ) {
        tc1.setText( tc2.getText() );
    }
}

TextSetterAction tf1tf2Setter = new TextSetterAction(tf1,tf2);
tt2.addActionListener( tf1tf2Setter );
tt3.addActionListener( new TextSetterAction(tf3, tf4) );
...

Of course, you can reuse objects, too:

tt4.addActionListener( tf1tf2Setter );
..

There are more ways to make life easier (e. g. JComponent's client
property) but it depends on the situation.

Bye
Michael

In Java, there is something called an anonymous inner class.

tt2.addActionListener(new ActionListener() {
   public void actionPerformed(ActionEvent e) {
       tf1.setText(tf2.getText() );
   }
 });

Oh, and a note on style.  It makes it a lot easier to
edit/debug/fix/maintain/describe your code if you use meaningful names.
tf1 is obscure, it should be named something like
"emailAddressTextField" where "emailAddress" is the "function" of the
text field.

names like tt2, tf1, tf2, all start to look the same after a while, and
if you're like me and continue coding after you start to get tired,
you'll start putting tt1 instead of tt2, etc.., and it can be difficult
to figure out where your mistake is.