Bad OOP design?

Question

I have to access some data before my program starts (to prevent a slow down while the program is running). The thing is, I need to init some objects before my program loads. It works fine now, but when I do the thing that I need the objects for, it hangs for a very short time (while it creates them, you see, right now I can only create them when the action they are needed for is called; it is to detailed to explain). The problem is it just looks unprofessional. Anyway, java.awt.component has a method that would make it possible for me to do the object creation before the program starts. Would it be bad to make a class that extends Component, and then define a method in there that get the information I need to makes it possible for me to create my object before the program starts? Is this bad OOP design?
Thank you!
Joshua

Answer 1

Of course you can't really initialize stuff "before your program loads" since the initialization is part of your program, just before you program tells the user it's loaded.
Probably the way to intialise stuff early is to do it in static, which will happen as soon as the class loads.
Mostly you can do it with static object variables initialised to new objects.
But you can get fancy and put a static code block in the class. Just a piece of code under
static {
  .. do some initialization