Warning trying to underline JLabel's text?

Question

Hello everyone. I've been trying to make the font of a JLabel underlined. I found this solution:Map map = myView.getMyJLabel().getFont().getAttributes();
map.put(TextAttribute.UNDERLINE, TextAttribute.UNDERLINE_ON);
myView.getMyJLabel().setFont(new Font(map));However, I can't make this 2 warnings dissapear:
Type safety: The method put(Object, Object) belongs to the raw type Map. References to generic type Map<K,V> should be parameterized.
Type safety: The expression of type Map needs unchecked conversion to conform to Map<? extends AttributedCharacterIterator.Attribute, ?>
I've also tried this:Map<TextAttribute, ?> map = myView.getMyJLabel().getFont().getAttributes();
map.put(TextAttribute.UNDERLINE, TextAttribute.UNDERLINE_ON);
myView.getMyJLabel().setFont(new Font(map));But in this case I get the following error:
The method put(TextAttribute, capture-of ?) in the type Map<TextAttribute, capture-of ?> is not applicable for the arguments (TextAttribute, Integer)
Does anyone know how can I get rid of this warnings or maybe, a simpler way to underline a JLabel's text?
Thanks in advance :)

Answer 1

1) During field validation (data entry error by the
user), the name of the field (via the registered
label) is used in the error dialog
2) During form validation (save button was
clicked), required fields that are still blank are
shown to the user in a dialog (again, using the text
of the field's label).
3) Required fields on the form get a red asterisk
for the label's icon that get turned off after the
field had been filled in. This is a requirement for
us, but I gather not an uncommon one. The presenter
informs the ui that a particular field
isRequired(true/false). The ui looks up the label
for that field and sets him to required(true/false),
which will turn the asterisk icon on/off.
In addition, we use JLabels for hyperlinks to other
forms in our app. Yes, they are underlined. Perhaps
not the best way to do it, but we subclassed JLabel
to return the non-html text on the call to getText(),
among other things.Ok, I think I get what you're talking about, but I think you're doingitwrong.com :P
The view has two purposes in my book, 1) to take input data from user, and 2) to give output data to user. Some components like text fields do both. Labels on the other hand, only do output. So back in the model, you have a name of an input field, which you stick in the label after doing some hyperlinky/red-asterisky/whatever presentation stuff to it.
IMHO, you should never be getting any data back from that view component. It's been tainted by transforming it for presentation. When you need to display that label's text elsewhere, you should go back to the model to get it, not the view. Only input data should come from the view. Since that label's output data, it should only ever go to the view.
I'm trying to be insulting or anything, since I know that this is a pretty academic argument I'm making, and we all live in the Real World. I'm just really interested in all this. Now I'm off on a 4 day weekend to Dragon-Con, see you suckers later!