MXML Editor does not work: no syntax highlighting, no code completion, nothing at all

[GoogleCodeExporter]

This is a VERY subtle bug. Infact we have two identical installation (one
is the copy of the other) on two identical systems (ubuntu feisty, java
1.6.0_20). 
In one system everything works correctly, except the embedded browser. In
the other one nothings works at all, except the embedded browser ...

So I have no idea on how to reproduce this problem, the only hint is this
error in the logs of the not working system:

Warning: Detected recursive attempt by part
com.adobe.flexbuilder.editors.mxml.MXMLEditor to create itself (this is
probably, but not necessarily, a bug)
Throwable: org.eclipse.ui.PartInitException: Warning: Detected recursive
attempt by part com.adobe.flexbuilder.editors.mxml.MXMLEditor to create
itself (this is probably, but not necessarily, a bug)
org.eclipse.ui.PartInitException: Warning: Detected recursive attempt by
part com.adobe.flexbuilder.editors.mxml.MXMLEditor to create itself (this
is probably, but not necessarily, a bug)
 at
org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.ja
va:586)

Original issue reported on code.google.com by vittorio.ballestra on 26 May 2010 at 10:13

[GoogleCodeExporter]

If you are using Flex SDK 4.0 and the old mxml namespace in fact there is no 
code
completion.
(Old namespace is: <mx:Application xmlns:mx="http://www.adobe.com/2006/mxml">)

In order to have your builder that work well you have to change it to
<mx:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
                xmlns:s="library://ns.adobe.com/flex/spark"
                xmlns:mx="library://ns.adobe.com/flex/mx">

It will involve also some other changes such as
<mx:Script>   --->    <fx:Script>
<mx:String>   --->    <fx:String>
<mx:Array>   --->    <fx:ArrayCollection>

Original comment by evrign...@gmail.com on 1 Jun 2010 at 8:20

[GoogleCodeExporter]

@to vittorio.ballestra

what the eclipse version?

Original comment by eshang...@gmail.com on 4 Jun 2010 at 9:38

[GoogleCodeExporter]

@to evrignaud : that's ok. But it's not this case.

I'm talking about a CORRECT project. that compiles and everything. If I open it 
with
fb4windoze it works. So it's not this simple. 

Original comment by vittorio.ballestra on 7 Jun 2010 at 5:17

[GoogleCodeExporter]

@to eshangrao

I'm with eclipse 3.5. I've noticed that the problem is somewhat minimized if we
create a new workspace with absolutely no project using a java nature.

Original comment by vittorio.ballestra on 7 Jun 2010 at 5:19

[GoogleCodeExporter]

with release 2010.06.04.1 when hitting CTRL+SPACE this is the stack trace:

!ENTRY org.eclipse.ui 4 0 2010-06-08 16:07:08.793
!MESSAGE java.lang.NullPointerException
!STACK 0
java.lang.NullPointerException
        at com.adobe.flexide.as.core.contentassist.ActionScriptCompletionProposal.apply(ActionScriptCompletionProposal.java:375)
        at org.eclipse.jface.text.contentassist.CompletionProposalPopup.insertProposal(CompletionProposalPopup.java:926)
        at org.eclipse.jface.text.contentassist.CompletionProposalPopup.access$21(CompletionProposalPopup.java:890)
        at org.eclipse.jface.text.contentassist.CompletionProposalPopup$2.run(CompletionProposalPopup.java:495)
        at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
        at org.eclipse.jface.text.contentassist.CompletionProposalPopup.showProposals(CompletionProposalPopup.java:482)
        at org.eclipse.jface.text.contentassist.ContentAssistant.showPossibleCompletions(ContentAssistant.java:1660)
        at org.eclipse.jface.text.source.SourceViewer.doOperation(SourceViewer.java:835)

Original comment by vittorio.ballestra on 8 Jun 2010 at 2:11

[GoogleCodeExporter]

Another stack trace :

java.lang.NullPointerException
    at com.adobe.flexbuilder.dcrad.core.DCRADContentAssistProcessor.getProposals(DCRADContentAssistProcessor.java:185)
    at com.adobe.flexbuilder.dcrad.core.DCRADContentAssistProcessor.computeCompletionProposals(DCRADContentAssistProcessor.java:124)
    at org.eclipse.jface.text.contentassist.ContentAssistant.computeCompletionProposals(ContentAssistant.java:1836)
    at org.eclipse.jface.text.contentassist.CompletionProposalPopup.computeProposals(CompletionProposalPopup.java:553)
    at org.eclipse.jface.text.contentassist.CompletionProposalPopup.access$16(CompletionProposalPopup.java:550)
    at org.eclipse.jface.text.contentassist.CompletionProposalPopup$2.run(CompletionProposalPopup.java:485)
    at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
    at org.eclipse.jface.text.contentassist.CompletionProposalPopup.showProposals(CompletionProposalPopup.java:479)
    at org.eclipse.jface.text.contentassist.ContentAssistant.showPossibleCompletions(ContentAssistant.java:1664)
    at org.eclipse.jface.text.source.SourceViewer.doOperation(SourceViewer.java:807)
    at org.eclipse.jface.text.source.projection.ProjectionViewer.doOperation(ProjectionViewer.java:1506)
    at com.adobe.flexide.editorcore.editor.FlexSourceViewer.doOperation(FlexSourceViewer.java:190)
    at org.eclipse.ui.texteditor.TextOperationAction$1.run(TextOperationAction.java:131)

Original comment by vittorio.ballestra on 8 Jun 2010 at 2:23

[GoogleCodeExporter]

This problem also occurs with:

eclipse 3.5 vanilla

eclipse 3.4 vanilla

Original comment by vittorio.ballestra on 8 Jun 2010 at 2:23

[GoogleCodeExporter]

Maybe I've found the problem: for some reasons some invalid builders where 
enabled on the project. After disabling them everything worked perfectly.

Just leave:
 - air project builder
 - flex builder
 - faceted project builder (I had two, after disabling both it worked but reopening project properties showed one of the two still enabled, probably reenabled by eclipse)

Original comment by vittorio.ballestra on 8 Jun 2010 at 2:43

[GoogleCodeExporter]

I can confirm this. After clean up my project, removing all unwanted builders 
everythings works very well.

You can close this.

Original comment by vittorio.ballestra on 11 Jun 2010 at 7:28

[GoogleCodeExporter]

thanks the reply!

Original comment by eshang...@gmail.com on 12 Jun 2010 at 2:01

• Added labels: fixed

[GoogleCodeExporter]

Sorry, but I was wrong.

Opened a new project and the bug is still there : no syntax highlight and no 
code completion at all. Even if this is a Flex-4 pure project.

nothing is working at all in the editor. and no exception are logged. We have 
experienced this problem in 2 different setup. 
I really wonder no one else did.

This thing is totally blocking and I can't even give an hint on how to 
reproduce or fix it. I'm really pissed off.

Original comment by vittorio.ballestra on 15 Jun 2010 at 4:12

[GoogleCodeExporter]

Some light is here !
I've created a new workspace from 0 and now that project is working.

So far my guess is : if you have an workspace where you ever open a java 
project then it will stop working for flex in some cases. This is what's 
happening for me.

Let's see if this theory will be confirmed in the next weeks of work ...

Original comment by vittorio.ballestra on 15 Jun 2010 at 4:18

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Yep : Confirmed.

Conclusion: Try to use fb4linux only in workspace where you have ONLY FLEX 
Projects.

Original comment by vittorio.ballestra on 29 Jul 2010 at 8:54

[GoogleCodeExporter]

I had many issues with this.  We use maven multi-module projects and had issues 
with our flex submodule. The syntax highlighting and content assist didn't work.
What we ended up doing (for now) is creating a new flex project (on it's own) 
and creating new source folders 'linked' to the real projects' source and lib 
folders.  Then i open teh files in the new project.  If they work there, then 
you can go back to the original project and they seem to work there too.

Original comment by treversh...@gmail.com on 14 Dec 2010 at 5:40