Yes, you can discover the available constructors and their parameters. But I don't think that it make sense in general to just pass null / 0 to parameters or guess at dummy values. It'd be as likely to cause even subtler errors.
I think what you have to do here is extend SnowballAnalyzer, where the subclass has a no-arg constructor which calls super(String) with the right argument. On Tue, Apr 20, 2010 at 7:57 PM, Robin Anil <robin.a...@gmail.com> wrote: > +dev > @Delroy: Well even if you did correct the spelling. I believe > SnowballAnalyzer cannot be instantiated without a parameter like > StandardAnalyzer. > > Constructor signature is: SnowballAnalyzer(String name); > @dev: I am not a java reflection expert. But is there a way we can find the > parameters of the constructor and automatically put some dummy values in it? > > Robin >
