It is nearly impossible to use the BeanInfo editor
to generate an
internationalized BeanInfo class - it hard-codes
strings for all
of the descriptions. It should offer the option
generating a bundle (including generating keys) or
adding them to an
existing bundle. This would make it much more
useful - as it is,
you have to generate the BeanInfo and then
manually remove the
//GEN-BEGIN, etc. comments and hand edit it to use
Changing to defect after consulation with nb QA and comments from nb
strategy that some i18n rfes could actually be viewed as defects. We
one is more like a defect so am changing it to that.
Let me know if more details are needed.
Consistent use of the I18N keyword.
I do not agree this is a defect; the user *is* able to produce I18Ned
beaninfo - by using e.g. bundle.getString("") instead of plain "".
What you are asking for is rather a quite large feature/rewrite than a