Use static method or not?

Question

Hi i have a web service in java, in which i have a class that has different methods that modify the string that the client sends and return it back according to the type of sting he wants. So based on the string type requirement a method is called..

like

class Test{

public static String a(String z)
{
 // do stuff and return;
}


public static String b(String z)
{
 // do stuff and return;
}
}

so if an array of like 10000 requests comes, these methods are called 10000 times, i want to know that should these methods be taken as static or NOT(i should create a global object of this class in my main web service class and call these methods) ?

kundan bora · Accepted Answer · 2012-05-08 05:13:02Z

2

I don't think you need to make method as static, if you can access the method within the object then you should (avoid static as much as possible).This improve code performance (in terms of memory utilization).

answered May 8, 2012 at 5:13

kundan bora

3,9392 gold badges22 silver badges29 bronze badges

Sign up to request clarification or add additional context in comments.

8 Comments

Harinder Over a year ago

yes i am thinking of crating a static object of this class in my main web service class, and use that to invoke these methods? would that be ok?

kundan bora Over a year ago

I think you have some confusion about static keyword. First thing is object itself can not be static (you can create static reference variable of an object). The terms static means you can acess class member directly with the reference of class (no need of object). in your scenario either you want to access method of Text class directly or you want to create an object and make its reference variable as static. let me know which option do you want ?

Marvo Over a year ago

I suspect he means he would create a static variable in the owning class to hold an instance of the class he's writing. Perhaps create a singleton instead.

kundan bora Over a year ago

Dennis using static reference variable in web service class will not give you any advantage.if you want a single instance of class to work on then you should use singleton pattern. you can find example here - javaworld.com/javaworld/jw-04-2003/jw-0425-designpatterns.html

Marvo Over a year ago

Does the class need to maintain any state from one invocation to the next? If so, then a singleton would work, or the class-variable-in-your-containing class would work. But from your description you didn't indicate you needed to retain data between invocations. However, it would probably save on object creations, depending on implementation.

|

Community · Accepted Answer · 2017-05-23 11:56:28Z

2

What's the compelling reason that these methods be static? If you need static methods, then create those. Otherwise, from a design standpoint, stick to non-static methods. You can't override static methods (though you can hide 'em.)

And there's this:

In Java, is there any disadvantage to static methods on a class?

edited May 23, 2017 at 11:56

CommunityBot

11 silver badge

answered May 8, 2012 at 5:19

Marvo

18.2k8 gold badges53 silver badges75 bronze badges

1 Comment

Harinder Over a year ago

would have accepted your ans also if accepting two were allowed.. thnks for ur help.. :)

Neel · Accepted Answer · 2012-05-08 11:21:14Z

1

You can use a static method if the method behaves the same for all cases. If the methods just does some work on the string supplied as a parameter and the behavior is the same for all instances, you can.

Again, you can also make a singleton out of it & call the methods through the UNIQUE_INSTANCE.

Something like:

public class Test {

    private static final Test UNIQUE_INSTANCE = new Test();

    private Test() {
    }

    public static final Test getUniqueInstance() {

        return UNIQUE_INSTANCE;
    }

    public final String a(String z) {

        // do stuff and return;
    }


    public final String b(String z) {

        // do stuff and return;
    }
}

Then you can do >>

Test.getUniqueInstance().a("Hello");
Test.getUniqueInstance().b("World");

edited May 8, 2012 at 11:21

Neel

2,1005 gold badges24 silver badges48 bronze badges

answered May 8, 2012 at 5:27

Rahul Thakur

94216 silver badges31 bronze badges

Comments

Bhavik Ambani · Accepted Answer · 2012-05-08 05:06:47Z

0

If there is not any resource which is shared among the threads then there is not harm to use any static method.

answered May 8, 2012 at 5:06

Bhavik Ambani

6,66515 gold badges58 silver badges87 bronze badges

Comments

Basilio German · Accepted Answer · 2012-05-08 05:22:37Z

0

Yes, there should be a Static modifier since there is no interaction between the different methods or functions, and the result is returned in the very same method. the "Static" word is to define a class variable or method that can be accessed without instantiating an object of such class.

if you do not intend to instantiate the class, and just need to use the methods inside, "Static" is the correct way to go, and set the class constructor to private.

edited May 8, 2012 at 5:22

answered May 8, 2012 at 5:15

Basilio German

1,8271 gold badge13 silver badges22 bronze badges

Collectives™ on Stack Overflow

Use static method or not?

5 Answers 5

8 Comments

1 Comment

Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

5 Answers 5

8 Comments

1 Comment

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related