Colour coding on Macromedia Flex (.mxml) files

[niklas]

Hi there,

I've managed to get tag insight working with Eclipse 3.1 and oXygen 6.2 however, I'm not getting colour coding happening and also I'm getting an org.apache.xerces.parsers.XML11Configuration error whenever I open .mxml files. However, if I open them in the text editor I'm fine.

Anyone seen this before?

Thanks

Niklas

[george]

Dear Niklas,

Please make sure you associate both the extension with the editor using the General / Editors / File Associations preference page and the extension with the Text/XML/oXygen XML content type using General / Content Types preference page.

The above should work but we experienced problems on one machine that had a lot of other plugins installed. Then we tried a clean Eclipse installation and that solved the problem.

A workaround for this issue is to edit the plugin.xml file and add the mxml extension to all the places where the xml extension is present then start Eclipse making sure the -clean parameter is passed in the command line. You can find such a modified plugin.xml here:
http://www.oxygenxml.com/update/mxml/plugin.xml

We do not have reports however about the parser configuration error. Do you have a stacktrace for that?

Best Regards,
George

[niklas]

Hi George,

Thanks for the help.

Adding the second file association to the General / Content Types preference page fixed the colouring and also made the other XERCES error go away.

However, whenever I open an MXML file now I get a "Content is not allowed in prolog." and it highlights the following line:



Code: Select all

<?xml version="1.0" encoding="UTF-8"?>

Any ideas? Do they mean prolog as in the programming language?

Thanks

Niklas

[niklas]

I lie, I'm still getting the XERCES error on some MXML files I open.

The error is being displayed in the "Problems" tab of Eclipse. Is there anywhere else I can look to get a better error?

[george]

Hi Niklas,

The "Content is not allowed in prolog" error means that there are some characters just before the XML header. If you send us a sample file at support at oxygenxml dot com we can look more into that.

If you see the error in the Problems View then it may be placed there by some builder of some other plugin. Look in the Error Log view to find details about the Eclipse errors.

Best Regards,
George

[niklas]

Hi George,

There seemed to be some encoding error problems and there was a funny character in front of the header.

Also, I've now got this error a few times:

"Could not create content describer for com.oxygenxml.editor.XmlFile. Content type has been disabled."

and the error debug:

Code: Select all

java.lang.ClassCastException: org.apache.xerces.parsers.XML11Configuration

at org.apache.xerces.parsers.DOMParser.<init>(Unknown Source)

at org.apache.xerces.parsers.DOMParser.<init>(Unknown Source)

at ro.sync.xml.encoding.D$_A.<init>(Unknown Source)

at ro.sync.xml.encoding.D$_A.<init>(Unknown Source)

at ro.sync.xml.encoding.D.A(Unknown Source)

at ro.sync.xml.encoding.D.A(Unknown Source)

at ro.sync.xml.encoding.D.A(Unknown Source)

at com.oxygenxml.editor.editors.xml.XMLContentDescriber.describe(Unknown Source)

at org.eclipse.core.internal.content.ContentType.describe(ContentType.java:162)

at org.eclipse.core.internal.content.ContentType.internalGetDescriptionFor(ContentType.java:448)

at org.eclipse.core.internal.content.ContentTypeCatalog.getDescriptionFor(ContentTypeCatalog.java:312)

at org.eclipse.core.internal.content.ContentTypeCatalog.getDescriptionFor(ContentTypeCatalog.java:316)

at org.eclipse.core.internal.content.ContentTypeMatcher.getDescriptionFor(ContentTypeMatcher.java:87)

at org.eclipse.core.internal.resources.ContentDescriptionManager.readDescription(ContentDescriptionManager.java:394)

at org.eclipse.core.internal.resources.ContentDescriptionManager.getDescriptionFor(ContentDescriptionManager.java:333)

at org.eclipse.core.internal.resources.File.getContentDescription(File.java:276)

at org.eclipse.ui.ide.IDE.getContentType(IDE.java:960)

at org.eclipse.ui.internal.ide.model.WorkbenchFile.getBaseImage(WorkbenchFile.java:34)

at org.eclipse.ui.internal.ide.model.WorkbenchResource.getImageDescriptor(WorkbenchResource.java:45)

at org.eclipse.jdt.internal.ui.viewsupport.JavaElementImageProvider.getWorkbenchImageDescriptor(JavaElementImageProvider.java:163)

at org.eclipse.jdt.internal.ui.viewsupport.JavaElementImageProvider.computeDescriptor(JavaElementImageProvider.java:117)

at org.eclipse.jdt.internal.ui.viewsupport.JavaElementImageProvider.getImageLabel(JavaElementImageProvider.java:92)

at org.eclipse.jdt.internal.ui.viewsupport.JavaUILabelProvider.getImage(JavaUILabelProvider.java:138)

at org.eclipse.jface.viewers.DecoratingLabelProvider.getImage(DecoratingLabelProvider.java:82)

at org.eclipse.jface.viewers.DecoratingLabelProvider.updateLabel(DecoratingLabelProvider.java:212)

at org.eclipse.jface.viewers.StructuredViewer.buildLabel(StructuredViewer.java:1855)

at org.eclipse.jface.viewers.TreeViewer.doUpdateItem(TreeViewer.java:228)

at org.eclipse.jface.viewers.AbstractTreeViewer$UpdateItemSafeRunnable.run(AbstractTreeViewer.java:85)

at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1044)

at org.eclipse.core.runtime.Platform.run(Platform.java:783)

at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:44)

at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:148)

at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:621)

at org.eclipse.jface.viewers.StructuredViewer$UpdateItemSafeRunnable.run(StructuredViewer.java:434)

at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1044)

at org.eclipse.core.runtime.Platform.run(Platform.java:783)

at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:44)

at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:148)

at org.eclipse.jface.viewers.StructuredViewer.updateItem(StructuredViewer.java:1763)

at org.eclipse.jface.viewers.AbstractTreeViewer.updateChildren(AbstractTreeViewer.java:1782)

at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefreshStruct(AbstractTreeViewer.java:1268)

at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1245)

at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1201)

at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart$PackageExplorerProblemTreeViewer.internalRefresh(PackageExplorerPart.java:518)

at org.eclipse.jface.viewers.StructuredViewer$8.run(StructuredViewer.java:1291)

at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1201)

at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart$PackageExplorerProblemTreeViewer.preservingSelection(PackageExplorerPart.java:624)

at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1289)

at org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider$3.run(PackageExplorerContentProvider.java:615)

at org.eclipse.jdt.internal.ui.packageview.PackageExplorerContentProvider$7.run(PackageExplorerContentProvider.java:659)

at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)

at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123)

at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3057)

at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2716)

at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1699)

at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663)

at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:367)

at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143)

at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103)

at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226)

at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376)

at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:585)

at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334)

at org.eclipse.core.launcher.Main.basicRun(Main.java:278)

at org.eclipse.core.launcher.Main.run(Main.java:973)

at org.eclipse.core.launcher.Main.main(Main.java:948)

[niklas]

From digging a bit deeper. The "Content is not allowed in prolog." is also shown when I open an MXML file with

Code: Select all

<?xml version="1.0" encoding="UTF-8"?>

in the top. When I remove it I don't get the error.

Any ideas?

Thanks for the help.

Regards

Niklas

[george]

Hi Niklas,

Thanks for providing more details. That looks like the content describer set by oXygen fails and then it is not able to ignore the byte order mark characters that probably exist before the XML header. Please get an updated oxygenEclipse.jar from the link below and replace the one from the oXygen plugin lib folder.

http://www.oxygenxml.com/update/6.2/oxygenEclipse.jar

Let us know how is going.

Best Regards,
George

[niklas]

Hi George,

Perfect. That fixed it!

No worries "Problems" or errors!

Thanks very much.

Will this be combined in the next update?

Regards

Niklas

[george]

Hi Niklas,

The jar I pointed you to was buit on the 6.2 branch. Sure, the fix will be merged in the main branch and will be available in all future releases.

Best Regards,
George