|Re: [EDAPT] EFactory questions [message #1711248 is a reply to message #1711028]
||Wed, 14 October 2015 10:10
| Maximilian Koegel
Registered: July 2009
sorry for the delayed reply. Johannes will get back to you today or tomorrow.
On 12.10.2015 15:28, Brad Schneider wrote:
> I am wondering if someone could explain a bit about how Edapt chooses an appropriate EFactory for
> loading an out-dated model during migration. From what I can tell at runtime, a default EFactoryImpl
> is being used. However, we have extra logic in our EFactory for the createFromString method, so I
> need a custom implementation.
> I'm trying to find if there is a "correct" or "most appropriate" way of handling this provided by
> the framework. If there is not a built-in method for handling this, will it be enough to retain a
> base version of the factory with the enhanced createFromString method, and register that to the old
> namespace URI(s) before migration? I haven't been able to find where the specific version of the
> EFactory to use for loading the old model is being set. Conceptually, I'm not certain on how I
> should expect Edapt to be able to handle this.
> Thanks for your help!
Get professional Eclipse developer support:
Powered by FUDForum
. Page generated in 0.02303 seconds