Community
Participate
Working Groups
The XML Schema editor's extension view depends on the XML document's content model to render the correct editing controls for fields (combo boxes will be shown when there are fixed values for fields). If I open an XML Schema and view the extension properties things will work as expected at first. However if I move to another editor to do other work and eventually come back to the extensions view I notice that the editor's control are created incorrectly as though the underlying content model has been lost.
This is a functional regression from WTP 1.5.x that seems to have been introduced by changes implemented for bug 139092.
Created attachment 70271 [details] undoes most of the change from bug 139092 I'm attaching a patch to roll back most of the changes that were made to fix bug 139092; we'll have to revisit them early in V3. It's pretty much a full undo except it retains Valentin's changes for bug 136399 where they overlapped.
Craig, I'm flagging you to review (you'll want to compare org.eclipse.wst.xml.core.internal.contentmodel.util.CMDocumentCache.java against its 1.2 revision for simplicity). Can you target this change for RC3?
Created attachment 70272 [details] rollback patch for tests Whoops, forgot to include the test plugins when generating the patch.
The rolled back changes look good. Marking for PMC approval.
Bad regression. Try to get this in for RC3.
Patches have been committed and released for WTP 2.0.
Closing.