|Re: [QVTo] Metamodels list "reloading" in QVTo plugin [message #726208 is a reply to message #726115]
||Fri, 16 September 2011 19:52
| Ed Willink
Registered: July 2009
Some tools search the workspace for models. Sometimes this is helpful,
usually it is inefficient and often confusing.
Other tools like QVTo expect you to identify the models.
If you want to do this dynamically put the relevant entries in the
ResourceSet's package registry that you share with QVTo.
On 16/09/2011 16:42, Piotr Zajaczkowski wrote:
> Thank you for answering my question.
> You wrote that the best method for registering metamodels is to
> register them on plugin start up. But how can I register metamodels
> that are dynamically created - as I wrote, the concrete form of these
> metamodels depends on some settings stored in my own files in
> workspace. Ok, I can iterate through all files in workspace on plugin
> start up and register all metamodels from them. But what should I do
> when user creates new file with new metamodel ? If I should not touch
> the registry in runtime, I can't see any other method for using these
> dynamically generated metamodels. Of course, I can store them in files
> in workspace but I would like not to do this. Enforcing to register
> them "as plugins" and running the new instance of Eclipse is also not
> Maybe it is possible to make my own files to be seen as metamodels by
> Qvto ? I mean - when Qvto plugin search the workspace for metamodels
> when resolving them, it calls some method which gives it a metamodel
> per each my file with dynamic metamodel settings.
> Or maybe there is a lot simpler solution ?
> Thanks in advance.
> Piotr Zajaczkowski
Powered by FUDForum
. Page generated in 0.10086 seconds