choices cannot be serialized, probably because the attribute "value" is of type EJavaObject.

Description

Choices cannot be serialized, probably because the attribute "value" is of type EJavaObject.

Change designdecision metamodel so that value is not serialized? Idea: Choice abstract und value derived. New subclass of Choice for GDoF that again allows arbitrary values?

Neue Unterklasse für Choice für GDoF die irgendwelche Werte enthalten kann…?

Error example: java.io.NotSerializableException: org.palladiosimulator.pcm.repository.impl.CompositeComponentImpl

See ResultsWriter class writeDSEIndividualsToFile(..)

Environment

None

Activity

Show:
Yves Kirschner
January 24, 2020, 12:55 PM

In order for serialization to work with Ecore-based models, a change to the design decision meta-model would be necessary. Since serialization works with simple CSV files, in agreement with Anne, Ecore-based serialization is not used for the time being for backward compatibility reasons.

Martina Rapp
January 17, 2020, 2:05 PM

This issue is still relevant and should be fixed, reconfirmed with Anne

Won't Fix

Assignee

Yves Kirschner

Reporter

Anne Koziolek

Labels

None

Requirement Category

None

External issue URL

None

Affects versions

Priority

Minor