mkornatzki wrote:PropertyDescriptor getPropertyDescriptors();
Gets the bean's PropertyDescriptors.
An array of PropertyDescriptors describing the editable properties supported by this bean. May return null if the information should be obtained by automatic analysis.
If not return null then only the properties in the array should be shown in the propertiesEditor in designer.
I think where we differ in our interpretation is your inclusion of the word "only
" in the above. You are reading an implicit "only" into the JavaDoc that we don't believe is there (or even should be there).
Currently, we treat the BeanInfo class as an override designed to either add additional special properties or customize specific existing properties. That is a much, much friendlier interpretation for most users (and custom component builders) than what you suggest. In fact, if you think about your interpretation, it means that even if all you want to do is add or customize a single property, you are now responsible for all of them. That is a lot of extra work and doesn't even address the issue of non-standard properties that are added via other means. Even your NetBeans screen shot shows additional properties listed beyond the single one that should be the only one listed according to you.
I would further suggest that our interpretation is the better one 99% of the time. We have dealt with hundreds of users thus far who have wanted to add or customize a property. Not one of them has asked us to only show that one property (until now).
mkornatzki wrote:Maybe this is a function that swingdesigner don't want to include (and that's the reason for the link of the customization api to create a bean with special annotations for swingdesigner) or i make a mistake.
The normal JavaBean API is actually quite limited in terms of what you can say about properties and only maps to a portion of the Customization API
that we support. We offer our own API to give the developer much better control over properties and editors than is possible using standard JavaBean techniques. You can certainly use standard JavaBean customization techniques, but we also allow you to go well beyond those.