For some reason, I started getting this weird problem when I ever try to define skinClass for my custom component.
Error message:
Problem:
"Content Assist" cannot work properly. See the Journal for more information.
And the log shows these two lines
"Content Assist" did not complete normally. See the journal for more information. java.lang.NullPointerException
I have googled, and some others also received an error message (with beta version of FB4). Here , a lot of people posted different methods, how they solved the problem, and it seemed to work for them, but none of the tricks worked for me.
Some of the solutions they posted here are
1) Quit FB 2) Delete this folder: .metadata\.plugins\com.adobe.flexbuilder.codemodel [in the top level
your workspace folder] 3) Restart FB
this fix seems to be only temporary. Once I imported some new assets from an assets SWC into my project, the error re-appeared. The quickest fix is to close and re-open the FB Project.]
I also get this problem when I import new assets from SWC or update MJK. To avoid the need to restart Eclipse or FB4 in general, I right-click on the Im project, working, go to properties, delete the folder containing my swcs and re-add them. This is pain, but it is faster than refusing to restart and reinitializing the IDE.
I get the same error after updating my SWC resources and I have an imported folder containing SWC. If I import only SWC, I do not get this error. My fix: import only SWC: s, not folders, or after updating SWC (when you imported the whole folder), move some in the path library list first and then down. This forces Flash Builder to update links or something like that. Anyway, this solves the problem
It seems that all (most?) Of them got this problem when they imported new assets (which is not in my case). My thing is different, not sure if he has something to do. Yesterday I installed perforce (version control software) and created a forforce workspace to save all my code (including flex). I added all the flex code to perforce and started working in the new perforce workstation instead of the original workspace. I checked only the "src" folder initially, because this is the only thing I'm going to make changes, but I think that this could create a problem for FB, because write permissions to the metadata folder may be required to save internal information.