Earlier versions of MyEclipse supported (or at least gracefully ignored) E4X syntactical constructs such as literal XML and the "for each" statement. MyEclipse 9 completely chokes on these constructs in both the editor and validation. Given the large amount of E4X code used in my project (which runs on the server inside of Rhino) , this make MyEclipse 9 very, very painful to use. Please fix this ASAP, or at least provide pointers to an alternative javascript plugin that can coexist gracefully with other MyEclipse components.

-Shon

svella,

I could replicate the issue at my end. I have filed a PR for the dev team to work on it.
Sorry for the inconvenience caused.

Shon,

Please refer to these posts for some background on changes to JS validation, between 8.6 and 9.0:

http://www.myeclipseide.com/index.php?name=PNphpBB2&file=viewtopic&p=123238#123238 and http://myeclipseide.com/index.php?name=PNphpBB2&file=viewtopic&p=122847&sid=b0eda194ad52876ee9458e127dc83cef#122847

I'm not aware of any free javascript plugins that can be used as alternatives but you can always try any that you find.

There are a couple of possible partial workarounds. You can turn off validation for the files that contain E4X. Also, if your E4X is in a <script> element, changing the type to "text/javascript;e4x=1" seems to remove the errors.

Eagerly awaiting the release of an improved editor and validator. In the mean time I've disabled javascript validation and am using the Aptana javascript editor.

Shon,

I'm glad you've found a way to keep working. Please look for improvements in this area in future releases.