This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Tomas, A little late, but here it is. I just tried another customizer today straight from O'Reilly's Java examples on writing customizers, and it did the same thing: properties change on the screen but no code is generated. Here's the conversation thread we had on this in January: David Pociu wrote: > When building a Customizer to deal with multiple > related properties of a bean, I want to know what > triggers the generation of code in Forte. The > GridBagLayout customizer is a good example of the > type of functionality I need in my own customizer, > in the sense that whenever a property is modified > in the customizer screen, code is also generated > for the setting of that property. I suppose your customizer class implements java.beans.Customizer interface. Forte then should add PropertyChangeListener to it and handle all changes your customizer fires. > I have succesfully generated code from a Property > Editor, by using the > public String getJavaInitializationString() > method to return the code that Forte generates for > that property, but had no luck with a Customizer. Bean customizer itself is not intended to provide any java code for the bean - it just sets properties for which code is then generated. If your bean can't be set using properties then it must be serialized... > In the customizer, I am currently able to change > the properties (and see the properties change in the > Component Inspector), but I don't know how to trigger > code generation by Forte from within the customizer > for the same properties. This is certainly a bug in Forte - if properties are changed in Component Inspector they should be also generated to code... Please file a bug to bugzilla (at http://w ww.netbeans.org/bugs.html). Thanks. - Tomas Pavek -------------------------------------------------- ------------------- To unsubscribe, e-mail: nbusers-unsubscribe@netbeans.org For additional commands, e-mail: nbusers-help@netbeans.org Reply Tomas Pavek 05:23am Jan 18, 2001 PST I forgot to mention - file the bug against "form" module, assign to me (tomas.pavek@netbeans.com). Tomas Pavek wrote: >> In the customizer, I am currently able to change >> the properties (and see the properties change in the >> Component Inspector), but I don't know how to trigger >> code generation by Forte from within the customizer >> for the same properties. > >This is certainly a bug in Forte - if properties are > changed in ComponentInspector they should be also > generated to code... Please file a bug to > bugzilla (at http://w ww.netbeans.org/bugs.html). Thanks.
OK, I'll look at it.
I think I've fixed it. Should be available in NetBeans 3.2 Beta build 6 (also in dev build). Could you verify the fix? Thanks.
Reopening, as it is not fixed entirely yet...
Hopefully fixed now (in trunk and release 32 branch).
verified
Unfortunatelly, this does not work again in 3.3.0. There's a security exception appearing suddenly, while the code in form module has not change since 3.2.1. Shame on us we did not notice this sooner - now it's too late to fix it. I'll use AccessController.doPrivileged call to process changes fired from bean customizer - to avoid security problems, although there should not be any, but we probably cannot rely on it... This will be fixed for NB 3.3.1. For NB 3.3.0, a workaround is to run IDE with: -J-Dnetbeans.security.nocheck=true
Fixed in dev and 3.3.1.
verified in [nb_dev](20020207)
Resolved for 3.3.x or earlier, no new info since then -> closing.