On May 24, 10:26 am, Thomas Kellerer <JUAXQOSZF...@spammotel.com>
wrote:
On 24.05.2007 16:18 Jason Cavett wrote:
I'm creating a system to parse various different files. Each file has
a certain format, so I have different parsers to handle each format
which is determined at runtime. Each parser is a subclass of
"FileParser." Additionally, each parser has a single constructor that
accepts three pieces of information (all the same information).
I am also creating an XML config file that holds information on the
parsers that are important to the application (as some applications
want certain parsers and others want other types of parsers - this
makes it simple to switch out the config file and so the correct
parsers are used).
What I'm wondering is, how do I instantiate these classes via Java
reflection? Normally when I use Java reflection, I have a default (no
arg) constructor. In this case, I have to pass in some information
before I can instantiate. Is this even possible?
I've searched for code examples online, but I can't find the
information I'm looking for. Any help would be much appreciated.
To make live easier I would create a setter to provide the three values
in the FileParser base class. The instance variables could be made
protected so that the subclasses can access them.
Then create an instance via reflection (default constructor), cast that
to FileParser and call the setter to pass the three values.
But you can also get a constructor with a certain number of parameters:
Class cls = Class.forName("ConcreteFileParser");
Class[] types = new Class[] { FirstParameter.class,
SecondParameter.class, ThirdParm.class };
Constructor cons = cls.getConstructor(types);
Object[] args = new Object[] { value1, value2, value3 };
FileParser p = (FileParser)cons.newInstance(args);
(Not tested)
Regards
Thomas- Hide quoted text -
- Show quoted text -
Your second method works (after some tweaking, of course). Thank you.
However, I had also been thinking about the first solution. But, I'm
trying to think about it this way - I won't be working on this code
forever, and I want to ensure that those values will be populated by
the next developer. (If they aren't, the FileParsing won't work.)
There's no way to ensure that those methods are called (or that the
variables are initialized) no matter what...is there?
haven't been initialized, and call it at the start of every public method.