Re: Generics and Polymorphism
On Apr 29, 3:52 pm, Daniel Pitts
<newsgroup.spamfil...@virtualinfinity.net> wrote:
Jason Cavett wrote:
On Apr 28, 8:14 pm, Daniel Pitts
<newsgroup.spamfil...@virtualinfinity.net> wrote:
Jason Cavett wrote:
I'm having some issues with generics and polymorphism. I thought th=
is
was possible in Java - maybe someone can clear up what I'm doing
wrong. Basically, when I actually try to use the preference, the co=
de
will not compile and I get the following error. How can I do what I=
'm
trying to do?
Here is the code that has the error:
PreferencesEnum.DERIVED_PREFERENCE.getPreference().setValue(new
String());
The error is:
The method setValue(capture#2-of ? extends Object) in the type
Preference<capture#2-of ? extends Object> is not applicable for the
arguments (String)
Thanks,
Jason
--- CLASS LISTINGS ---
I have an enum:
PreferencesEnum {
DERIVED_PREFERENCE(new DerivedPreference());
private final Preference<? extends Object> pref;
private PreferencesEnum(Preference<? extends Object> pref) {
this.pref = pref;
}
public Preference<? extends Object> getPreference() {
return pref;
}
}
The problem is that DERIVED_PREFERENCE.getPreference() returns
Preference<? extends Object>, who's setValue() method accepts only E,
which can't be statically determined from the context...
Another issue is that enums can't have type parameters, so that makes
what you're trying to do specifically impossible using "enum"......
What you *can* do is instead of "enum", use a plain old class.
class PreferencesEnum<E> {
private final Preference<E> pref;
public static final DERIVED_PREFERENCE = new
PreferencesEnum<String>(new DerivedPreference());
private PreferenceEnum(Preference<E> pref) {
this.pref = pref;
}
}
etc...
Hope this helps.
Alright. It did help and I appreciate it.
The solution does seem a little clunky, however. Not being able to
paramaterize enums is kind of painful. Is there another possible way
of handling preferences that I'm not seeing? Basically, I want to
avoid having a huge file that contains every individual preference
(which is what was in place originally). Trying to edit that file was=
a nightmare.
Either way, this solution works. Thanks again, Daniel.
Are they truly preferences, or are they configuration? If its actually
configuration, you could try using Properties and/or a XML Spring containe=
r.
Alternatively, you can have a less generic Preferences class that has
fields and getters/setters for each preference that can be set.
The third approach is to use a EnumMap<PreferenceType, Object>, but you
don't get the type safety.
--
Daniel Pitts' Tech Blog: <http://virtualinfinity.net/wordpress/>
I'm not sure what you mean by preferences vs. configuration.
(However, intuitively, I would say that these are preferences.)
When you say, "you can have less generic Preferences class..." do you
mean, I don't program to a generic interface and, instead, each
preference object has a similar naming scheme, but each knows exactly
what it has to set and get?
class Preference1 {
void set(String blah) ...
String get() ...
}
class Preference2 {
void set(Boolean blah) ...
Boolean get() ...
}
Something along those lines?
Thanks again for your help.