Comments on: Quick Tip 25: New Persistence in 6.7 Window System http://eppleton.sharedhost.de/blog/?p=619 Toni's blog on NetBeans and Java Thu, 09 Sep 2010 12:07:20 +0000 http://wordpress.org/?v=2.7.1 hourly 1 By: Toni http://eppleton.sharedhost.de/blog/?p=619&cpage=1#comment-4866 Toni Fri, 21 Aug 2009 08:55:44 +0000 http://eppleton.sharedhost.de/blog/?p=619#comment-4866 I also ran into the "Twingleton" bug several times in the meantime :-). It's really ugly. Thanks a lot for the update. I also ran into the “Twingleton” bug several times in the meantime :-). It’s really ugly. Thanks a lot for the update.

]]> By: Aljoscha Rittner http://eppleton.sharedhost.de/blog/?p=619&cpage=1#comment-4865 Aljoscha Rittner Fri, 21 Aug 2009 08:51:58 +0000 http://eppleton.sharedhost.de/blog/?p=619#comment-4865 Hi! The current created TopComponent template by the wizard is buggy. The current template destroys the singleton pattern (the TopComponent is created twice). I've a solution described in my (german) blog: http://www.sepix.de/blogs/blogrittner/blog/archive/2009/august/21/beandev_convertasproperties_zerstoeren_singleton_pattern_von_topcomponents/index.html In short, please replace the generated readProperties method by this little correction: Object readProperties(java.util.Properties p) { if ( instance == null ) { instance = this; } instance.readPropertiesImpl(p); return instance; } br, josh. Hi!

The current created TopComponent template by the wizard is buggy. The current template destroys the singleton pattern (the TopComponent is created twice). I’ve a solution described in my (german) blog:

http://www.sepix.de/blogs/blogrittner/blog/archive/2009/august/21/beandev_convertasproperties_zerstoeren_singleton_pattern_von_topcomponents/index.html

In short, please replace the generated readProperties method by this little correction:

Object readProperties(java.util.Properties p) {
if ( instance == null ) {
instance = this;
}
instance.readPropertiesImpl(p);
return instance;
}

br, josh.

]]>