Dependency graph between resources in a resourceSet [message #1828690] |
Tue, 16 June 2020 11:46  |
Eclipse User |
|
|
|
Hi,
In my ResourceA I have object that references an object in the resource B inside may resourceSet.
So my ResourceA depends of ResourceB.
Do you know if exist a method or a simple process to find directly between dependencies between resources?
Thanks for your response.
|
|
|
|
|
|
|
|
|
Re: Dependency graph between resources in a resourceSet [message #1832150 is a reply to message #1832023] |
Thu, 10 September 2020 04:26  |
Eclipse User |
|
|
|
Hi
I think the challenge was to Ed W rather than Ed M.
Graph algorithms are a huge area for which it would be impossible and very undesirable to include every possible algorithm in EMF.
Your challenge doesn't define what you mean by dependency, so it is hard to answer.
Ed M has sensibly answered for a Resource-to-Resource dependency.
In my code I am often concerned with Type-Use-to-Type-Declaration dependency and providing forward declarations to avoid forward references. This is often requires type declarations to be intermingled Resource-wise. Templated operations can make life quite complex.
If you are able to produce generally useful routines, publicising them on this forum may be useful. If you can step back or or get a colleague to give an objective assessment of the utility, it may be worth raising a Bugzilla.
After 20 years of usage, it could make a very interesting research project to mine EMF clients for general purpose routines that could be considered for promotion to EcoreUtil. But that requires not just the time and familiarity to do the mining, but also the time and skill to rationalize each candidate into a uniform general purpose style suitable for EMF. Almost every candidate will be at least to some extent dependent on the design policies of the EMF client which often exclude the generality of EMF. Many other candidates may be useful with the derived type system of the client, but become a troublesome once templated into a 're-usable' form. Just take a look at the 10-long template parameters in org.eclipse.ocl that supported use in conjunction with both Ecore and UML metamodels. Sometimes more re-usable means less useable, so a library of code for clone and edit is often the best re-use.
Regards
Ed Willink
|
|
|
Powered by
FUDForum. Page generated in 0.33871 seconds