|
|
Re: StackOverflowError on EPackageRegistryImpl [message #1767448 is a reply to message #1767430] |
Thu, 06 July 2017 04:19  |
Eclipse User |
|
|
|
Hi
Increasing the stack size may well make the problem go away. Not having both autosar402 and autosar403 installed may help. But fundamentally the very dubious practice of a huge number of nested installed packages appears to expose a weakness in the autogenerated Java EPackage initialization. It appears that many packages are ensuring that many other packages are initialized first in such a complex fashion that the stack trace duplicate entry detector fails to spot the duplicates. This appears to be poor AUTOSAR design in that everything depends on everything in a too cyclic graph rather than a directed tree. It is actually possible to get this problem with just EMF plus one other EPackage; it is solved by ensuring that EMF is explicitly initialized first.
Since you probably do not want to redesign AUTOSAR, I suggest that you write an AUTOSARResourcesUtil.init() that ensures that each AUTOSAR package is initialized in a disciplined order. Similar to UMLResourcesUtil.init() it can probably do quite a lot of other useful initialization jobs. Maybe it already exists and you neglected to call it.
Regards
Ed Willink
|
|
|
Powered by
FUDForum. Page generated in 0.04083 seconds