getConfig() as a Static

So, I'm making a new plugin, but I call a string from my config twice. Now, as most of you know getConfig() can never be static, so how would one go about this? Here's the code BTW:

Code:java

String database = getConfig().getString("DatabaseName");

 

Can you explain more? Do you mean you are trying to access getConfig() in a different class rather than the main? Or...?

 

I am trying to access it more than once on the main

 

1Achmed1
So the problem is..?

Also, how can't getConfig() be accessed in a static manner?

Code:java

public static FileConfiguration config = getConfig();

 

Put this code into Eclipse:

Code:java

static String database = getConfig().getString("DatabaseName");

 

1Achmed1
Oh, whoops, I forgot you can't do that.. Here's a work-around:

Code:java

    public static String database;
 
    @Override
    public void onEnable()
    {
        database = getConfig().getString("DatabaseName");
    }

 

Thankssss

 

Why would you ever need to access it statically?

 

In my plugin I access it twice within the same class.

 

1Achmed1
Do you know the definition of static?

 

Code:java

static

Is a keyword that can be used in 3 scenarios:

• static variables
• static methods
• static blocks of code

Static Variables (Our form of static)
Static variables that belong to the class, not to an Object(instance)

Static variables are initialized only once, at the start of the execution. These variables will be initialized first before the initialization of any instance variables

A single copy to be shared by all instances of the class --> What we are using the keyword for

A static variable can be accessed directly by the class name; It doesn't need any object


If that's what you wanted?

 

1Achmed1 Thank you! I always had curiosity, but I never had googled it.

 

1Achmed1
Very good, but the one issue is, you don't need static variables for what you're doing..

 

The_Doctor_123 You only need it if you are using static methods.

 

PatoTheBest
Very true, but he hasn't told us that. Here's what he said:

Of course, maybe he isn't being specific enough.

 

Pass the configuration (or the plugin itself) down the stack in the constructors.

Singletons are bad. Never use them, especially in a non-singleton environment like the Bukkit API. This applies to static variables that are directly modified by a non-static call.

 

Coelho
I'm always creating a static variable instance and fill it in onEnable() and set it to null in onDisable(). I had no problems.

 

This is incorrect practice and I will continue to shun anyone who does this for their complete lack of knowledge regarding the Java programming language.

 

Coelho
be happy that I let varaibles start lowercase and classes uppercase ((((((((((((((((((((((

 

Pass the same FileConfiguration object to every instance of the class....
Creating a static FileConfiguration is a bad, improper use and should be avoided. The config is a single instance of an object and should not be used statically. Like I said before. Pass over the same variable.