Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse Platform » ModelProvider.validateChange limitations
ModelProvider.validateChange limitations [message #675361] Tue, 31 May 2011 09:27 Go to next message
Franck Mising name is currently offline Franck Mising name
Messages: 91
Registered: July 2009
Location: France
Member
Hi all,

The "Model Roadmap for Logical Model Integration" has some very useful information on how to properly integrate an abstract model into Eclipse.

Unfortunately, the ability to validate operations performed on our model's resources using a ModelProvider is severely limited by the fact that its validateChange method is far from being called for all modifications.
Browsing through the code it seems that ModelProvider.validate change is essentially only called from IOperationHistory.execute, and there are many scenarios in which resource modifications are not going through that method.

For example it was decided that File/Folder creation should not be undoable anymore in 3.5, and following that change our ModelProvider is not consulted anymore when Project->New Folder is invoked in our projects.

It seems that the validation by a model provider has nothing to do with undo/redo or the operation history, is there a way the consultation of model providers could be made more universal?
Other typical use cases include refactoring operations, editors Save As, drag&drop...
Maybe WorkspaceModifyOperation would be the right place to consult the model provider?
Re: ModelProvider.validateChange limitations [message #676184 is a reply to message #675361] Fri, 03 June 2011 06:29 Go to previous messageGo to next message
Franck Mising name is currently offline Franck Mising name
Messages: 91
Registered: July 2009
Location: France
Member
Anyone? Should I file a defect?
Re: ModelProvider.validateChange limitations [message #756802 is a reply to message #676184] Tue, 15 November 2011 07:45 Go to previous messageGo to next message
Franck Mising name is currently offline Franck Mising name
Messages: 91
Registered: July 2009
Location: France
Member
I have entered bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=348360 - still no comment here or in the defect.

This issue is making ModelProviders pretty useless and is seriously affecting the integration of 3rd party logical models, is there any chance someone could at least confirm that that framework is still being maintained?

Thanks!
Re: ModelProvider.validateChange limitations [message #756880 is a reply to message #756802] Tue, 15 November 2011 12:28 Go to previous messageGo to next message
Paul Webster is currently offline Paul Webster
Messages: 6859
Registered: July 2009
Location: Ottawa
Senior Member

Core Resources is still being worked on, if that's what you are asking.

PW


Re: ModelProvider.validateChange limitations [message #756944 is a reply to message #756880] Tue, 15 November 2011 16:14 Go to previous message
Franck Mising name is currently offline Franck Mising name
Messages: 91
Registered: July 2009
Location: France
Member
I am asking if core operations, ltk refactorings, and other Eclipse supplied frameworks that modify resources are still supposed / expected to check for a model provider and consult its validateChange method before changing a resource?
This is documented, the JDT refactorings do it, the history operations do it (see defect), but some operations have stopped doing it since Helios (see defect).
Previous Topic:a feature project including sources
Next Topic:Retrieve the AbstractUIPlugin from Bundle
Goto Forum:
  


Current Time: Mon Sep 22 20:24:19 GMT 2014

Powered by FUDForum. Page generated in 0.09558 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software