[Panagiotis Korros]

I experience a very big delay the first time i open a file in the myeclipse xml editor.

to find out what was going wrong I opened eclipse with the -console argument and took a stack trace.

Here is a sample of what I saw:
at org.eclipse.core.internal.resources.File.setCharset(File.java:362)
at org.eclipse.ui.editors.text.FileDocumentProvider.persistEncoding(FileDocumentProvider.java:819)
at org.xmen.ui.XMLDocumentProvider.createDocument(Unknown Source)
at org.eclipse.ui.editors.text.FileDocumentProvider.createElementInfo(FileDocumentProvider.java:544)

I think that the xml editor tries to set the document encoding. The call to FileDocumentProvider.persistEncoding takes a large amount of time to complete because it initializes my team provider etc.

The myeclipse xml editor for Eclipse 3.0 does not need to call this method since eclipse does a very good job at determining the encoding from the stream contents. This call should be removed in MyEclipse 3.x.x releases.

Also there is no need for the ‘suppress warning for non-default file encoding’ for Eclipse 3.0 and should be removed in MyEclipse 3.x.x releases.

[Scott Anderson]

Good points. I added an enhancement request for the 3.0 branch and referenced this thread. Thanks for the feedback to help us improve.

[Author]

Posts