Inheritance and polymorphism in static method

[Vodka]

Hello,
I have a problem a bit special, in fact not a real problem but rather a concern that I design because I love solving perfection. I have a class called 'vegetable' which contains a static method named 'getFoo ()' that returns an integer. I now creates a carrot and cabbage class that inherits from vegetable and method overloading 'getFoo' by returning different values each. I have a method in another class completely independent of the schematic revision named 'processFoo' here is the prototype:

public void processFoo (Vegetable vetg);

I'd like to access a static method of a class corresponding to an object instantiated. but it is not accessing it. If you have any solution for this then it would be great. Thanks in advance.

[NetWorkInG]

Hello,
I think you mix static and instance methods. A static method is independent bodies. You use an instance of an object, and you want to execute a method in this instance it is a dynamic execution. By calling via reflection a static method, you simulate the behavior of the dynamic execution in a static concept, and this must surely be far less "efficient" that uses a dynamic method (which is fine by optimizing the JVM ).

[ISAIAH]

Hello,
I think even I have a similar kind of a problem with my code. For, while programming object, many Java developers make the mistake of forgetting the concept of static element and is found with objects instantiated multiple times without any need! ... while the static concept is extremely useful to be really efficient OOP, including classes using the singleton or other pattern like that. I guess I am correct here, and if I am not then please guide me with correct.

[Linux-Us]

Hello,
I have nothing against static elements when necessarily. But in this case it looks more like a simulation of dynamic invocation ( call a static method differs depending on the actual type of an instance). In this case there is no reason to be static. What I meant is that the dynamic invocation is a cornerstone of OOP (especially Java), and if you want to do without it for X or Y because it is better to change the language.

[HardWeaR]

Hello,
I find that static methods are impractical in java, and I use them only for some sort of utility class. The inheritance and polymorphisms in particular are very badly managed, in my opinion. So for your case, or I need the inheritance, and then I would make the method getFoo instance method, benefiting the whole body mechanics, or I give them a special signature for each class, for example getFooDeClass1 () getFooDeClass2 (), etc.. This amounts to a little tone getFoo (Class1 fooType), except that it is more radical.

[cyber-noob]

Hello,
It is already possible with Generics for Java 5.0.

The inheritance and polymorphisms in particular are very badly managed, in my opinion.

At the same time static means we are not bound to an instance ... So you can not really talk about inheritance. Returning to the problem was what to serve it all about?