Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

DefaultPersistentEObject.toString() throws a StackOverflowError on EClass instances #80

Closed
gdaniel opened this issue Jun 22, 2017 · 1 comment
Closed

DefaultPersistentEObject.toString() throws a StackOverflowError on EClass instances #80

gdaniel opened this issue Jun 22, 2017 · 1 comment
Assignees
@gdaniel
Labels
Component: Core Type: Bug

Comments

@gdaniel
Copy link
Contributor

gdaniel commented Jun 22, 2017

This error occurs when using generated NeoEMF code from the Ecore metamodel: if a toString() call is performed on an EClass instance, the method will fall in an infinite loop trying to get the eClass() of the current EClass.

Should be easy to fix by removing internal toString() calls.
@gdaniel gdaniel self-assigned this Jun 22, 2017
gdaniel added a commit that referenced this issue Jun 22, 2017
@gdaniel
merge DefaultPersistentEObject.toString fix (refs #80)
cf04b8d
@gdaniel
Copy link
Contributor Author

gdaniel commented Jun 22, 2017 •
edited
Loading

Fixed by calling e(Dynamic | Static)Class.getClass().getCanonicalName() instead of e(Dynamic | Static)Class.toString() see bbc5f7a

@gdaniel gdaniel closed this as completed Jun 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gdaniel gdaniel

Labels
Component: Core Type: Bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gdaniel