Product Version: NetBeans IDE 6.0 (Build 200711261600)
Java: 1.5.0_07; Java HotSpot(TM) Client VM 1.5.0_07-87
System: Mac OS X version 10.4.11 running on i386; MacRoman; en_US (nb)
1. Download the facelets 0.6 module from nbfaceletssupport.dev.java.net, install it in the IDE
2. Register GlassFish v2 in the IDE
3. Create a new web project with Facelets framework enabled (accept all defaults)
4. Create a new Facelets template (CSS layout, layout with header, footer and left menu)
=> Deadlock, see attachment
Created attachment 53605 [details]
Deadlock thread dump
looks like editor infrastructure issue
Well, I'm not sure if initializing colorings from SLanguageProvider.findLanguage is really necessary. IMO the
initialization of Schliemann languages is still flaky. Simple calls like finding a lexer do not necessarily need to
initialize every feature of the language.
I might try to prevent the deadlock by not calling the highlight layer factories under the lock in HighlightingManager.
The small inefficiency in possibly creating multiple versions of the layers and then throwing them away is probably
Probably not fixed just by this, but should be better.
Checking in LexerBasedHighlightLayer.java;
new revision: 1.3; previous revision: 1.2
Is the deadlock still reproducible after Vita's fix?
Created attachment 56229 [details]
The crash of nbfacelets plugin
I tried repeating the steps, but the facelets plugin crashed in the step #3. See the messages.log attached.
Vito, you probably download the plugin for NB 5.1 not for NB 6.0. You should try the snapshot 6. This build contains
some synchronization issues and from the attached deadlock stacktrace it can be already fixed.
Ah, right, now I have the plugin version for Nb6 and it seems to work fine. All steps passed, no deadlock. I'm
reassigning this back to the editor and closing it as fixed. For anybody trying to follow the steps make sure that you
download the right plugin version. You are looking for something like this when installing to Nb6.x:
Seems to work fine now.