views:

86

answers:

4

Hello everybody,

How can I loop over a class attributes in java dynamically.

For eg :

public class MyClass
{
private type1 att1;
private type2 att2;
...
public void function()
{
    for(var in MyClass.Attributes)
    {
       System.out.println(var.class);
    }
}

}

is this possible in Java?

+3  A: 

Java has Reflection (java.reflection.*), but I would suggest looking into a library like Apache Beanutils, it will make the process much less hairy than using reflection directly.

Tassos Bassoukos
+6  A: 

There is no linguistic support to do what you're asking for.

You can reflectively access the members of a type at run-time using reflection (e.g. with Class.getDeclaredFields() to get an array of Field), but depending on what you're trying to do, this may not be the best solution.

See also

Related questions


Example

Here's a simple example to show only some of what reflection is capable of doing.

import java.lang.reflect.*;

public class DumpFields {
    public static void main(String[] args) {
        inspect(String.class);
    }
    static <T> void inspect(Class<T> klazz) {
        Field[] fields = klazz.getDeclaredFields();
        System.out.printf("%d fields:%n", fields.length);
        for (Field field : fields) {
            System.out.printf("%s %s %s%n",
                Modifier.toString(field.getModifiers()),
                field.getType().getSimpleName(),
                field.getName()
            );
        }
    }
}

The above snippet uses reflection to inspect all the declared fields of class String; it produces the following output:

7 fields:
private final char[] value
private final int offset
private final int count
private int hash
private static final long serialVersionUID
private static final ObjectStreamField[] serialPersistentFields
public static final Comparator CASE_INSENSITIVE_ORDER

Effective Java 2nd Edition, Item 53: Prefer interfaces to reflection

These are excerpts from the book:

Given a Class object, you can obtain Constructor, Method, and Field instances representing the constructors, methods and fields of the class. [They] let you manipulate their underlying counterparts reflectively. This power, however, comes at a price:

  • You lose all the benefits of compile-time checking.
  • The code required to perform reflective access is clumsy and verbose.
  • Performance suffers.

As a rule, objects should not be accessed reflectively in normal applications at runtime.

There are a few sophisticated applications that require reflection. Examples include [...omitted on purpose...] If you have any doubts as to whether your application falls into one of these categories, it probably doesn't.

polygenelubricants
in fact, according to value of fields, I want to write or not write the value of each field?
Zakaria
@Zakaria: yes, you can accomplish this with reflection, but depending on what is it that you're trying to do, there are much better designs.
polygenelubricants
In fact, I have a report to generate from a class, and depending on the value of class fields I want to put or not those fields, what's the best design that can I implement.?
Zakaria
@Zakaria: Unless you want a general purpose highly customizable class report generator that works with _any_ class, you should just stay away from reflection and just write a specific taylor-made solution for this particular class in your application domain.
polygenelubricants
What I want to do is to test on field value, if isn't null I want to include it in report and vice versa. I have a lot of attributes and I don't want to test them all manually so I thought that using reflection will resolve the problem.I will use it in one class.I just want to add that the result of this function is an array of String. (String[])
Zakaria
@Zakaria: go ahead and try reflection out then. There's `Field.get` that you can use to read the values of a field reflectively. If it's `private`, you may be able to get around that with `setAccessible`. Yes, reflection is very powerful and it lets you do things like inspecting `private` fields, overwriting `final` fields, invoking `private` constructors, etc. If you need further assistance with the design aspect, you should probably write a new question with a lot more information. Perhaps you don't need these many attributes in the first place (e.g. use `enum` or `List`, etc).
polygenelubricants
+3  A: 

Accessing the fields directly is not really good style in java. I would suggest creating getter and setter methods for the fields of your bean and then using then Introspector and BeanInfo classes from the java.beans package.

MyBean bean = new MyBean();
BeanInfo beanInfo = Introspector.getBeanInfo(MyBean.class);
for (PropertyDescriptor propertyDesc : beanInfo.getPropertyDescriptors()) {
    String propertyName = propertyDesc.getName();
    Object value = propertyDesc.getReadMethod().invoke(bean);
}
Jörn Horstmann
yup, much better style! +1
seanizer
A: 

While I agree with Jörn's answer, there is a more elegant possibility if you use spring.

Spring has a class named ReflectionUtils that offers some very powerful functionality, including doWithFields(class, callback), a visitor-style method that lets you iterate over a classes fields using a callback object like this:

public void analyze(Object obj){
    ReflectionUtils.doWithFields(obj.getClass(), new FieldCallback(){

        @Override
        public void doWith(final Field field)
            throws IllegalArgumentException, IllegalAccessException {

            System.out.println("Field name: " + field.getName());
            field.setAccessible(true);
            System.out.println("Field value: "+ field.get(obj));

        }
    });
}

But here's a warning: the class is labeled as "for internal use only", which is a pity if you ask me

seanizer