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.

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

Setup New Architecture #6

Open
2 tasks
isalvadori opened this issue Jul 30, 2024 · 0 comments
Open
2 tasks

Setup New Architecture #6

isalvadori opened this issue Jul 30, 2024 · 0 comments
Assignees

Comments

@isalvadori
Copy link

isalvadori commented Jul 30, 2024

We realized the current architecture is too complex, thus, with the aim of simplifying it, we try to make some changes. In particular:

  • We want to use a structure similar to the one used in our emf.osgi for the ModelInfo: when a new EPackage comes around, we want to create a CodecModelInfo object which loops over the various EClass, EFeature etc, and construct the corresponding IdentityInfo, TypeInfo, etc, which will then be used by the CodecModule and the ObjectMapper for serialization and deserialization;
  • This should reduce the current complexity of having the *Info and *Property objects and creating the ObjectPropertyMap for every object we want to serialize/deserialize;
  • The idea then would be that, when we want to serialize an EObject belonging to a given EPackage we should be able to retrieve a corresponding instance of CodecModelInfo for that EObject, and overwrite, if needed, the default setup, like the id or type key names to use during serialization, etc.

The steps to achieve that would be:

@isalvadori isalvadori self-assigned this Jul 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant