How do i make the program hold after it has created a JFrame

Question

I have created a JFrame with which the user shall login to a server. I call this JFrame from my main method (the JFrame-class is in a separate file). My problem is that after the login-window is created and set visible, my main method continues, i would like it to wait until the user have logged in before running the rest of the code.
this i my main method:
new LoginWindow();
System.out.println("Logged in: "+Session.isLoggedin()+
                "\nUsername: "+Session.getUsername());Session.isLoggedin() returns a boolean, true if user is logged in and otherwise false. class LoginWindow extends JFrame.
i have tried to use a while-loop to solve my problem:
while(!Session.isLoggedin()) { }and also
whiel(true){
    if(Session.isLoggedin())
        break;
}these while-loops never breaks, i have waited for about 3 min after successful login.It isn't because Session.isLoggedin() returns false, it does return true after a successful login (i've checked).
the funny thing however is if i print something in the while-loop i does break when login is finished
example:
whiel(true){
    System.out.println(Session.isLoggedin());
    if(Session.isLoggedin())
        break;
}this code makes the program wait until the login-phase is complete but i don't want it to print "text" a few thousand times while the user is logging in. (i've used "hej" as output aswell)
Since i have no idea how long it will take for a user to log in i can't use the System.sleep(value) method.
I would really appreciate any help
Thanks in advance
//Oscar

Answer 1

SnuShogge wrote:
I am still curious about why the while-loop only breaks if i print something using System.out.println(""), i didn't think that would make a difference since the break-statement remains the same.In general you should avoid trying to use while (true) or its variants in a Swing GUI as it often messes with the EDT, the main thread that renders the GUI graphics and interacts with the user.
My problem i however partially solved by using a JDialog instead of a JFrame. I am planning on using JFrame later in the program so the problem might come back to haunt me if it isn't solved.This may not be a great idea. Usually an application has one single JFrame. Most other distinct windows a dialogs of one sort or another and should be JDialogs, not JFrames. Often better still is to use a CardLayout to swap JPanels or other components.