Re: Problem: Calling methods of dynamically loaded inner classes at runtime
Thea wrote:
} catch (Exception e) {
e.getMessage();
}
You seem to be discarding errors silently -- not the best way to find out
what's going wrong ;)
//making sure that calling execute routine makes sense
if (attributeObject instanceof Module)
((Module)attributeObject).execute(page, request,
Again, you are supressing errors silently. The guard test may make sense for
deployed code but it is /currently/ preventing you from seeing any errors.
Actually, unless the design requires cases where the loaded classes may not
implement Module, then the test would probably be unwise even in deployed
code -- for exactly the same reason.
Map attrs = page.getAttributes(); //here I get names of
classes to be loaded
//names are obtained correctly, checked that (correctly==as provided in
config file)
It's possible that you are specifying the wrong names for the inner classes.
The /real/ name of a class defined as:
package my.stuff;
class Outer
{
class Inner { }
}
is something like my.stuff.Outer$Inner. See the name of the classfile to see
what you /should/ be providing.
Also:
Constructor attributeCon = attributeClass.getConstructor();
Object attributeObject = attributeCon.newInstance();
If your "inner" classes really are inner, rather than just static nested
classes, then none of them will have a no-args constructor. All non-static
nested classes require a pointer to their outer object, and that is passed in
as a (hidden) parameter to each constructor, which is added by javac. When you
call the constructor in normall code the compiler automatically adds a ref to
the outer object to the parameters you pass -- but if can't do that when you
are using reflection.
Given that you expect the above to work at all, it sounds as if your design
really calls for the nested classes to be static, in which case your use of
Constructors should work as is. If not then you'll have to change the
reflective code accordingly.
-- chris