User Story #165 (closed)
Opened 18 years ago
Closed 18 years ago
Fix model serialization
Reported by: | jamoore | Owned by: | jamoore |
---|---|---|---|
Priority: | blocker | Milestone: | 3.0-M3 |
Component: | Remoting | Keywords: | serialization, testing, iteration4 |
Cc: | Story Points: | n.a. | |
Sprint: | n.a. | Importance: | n.a. |
Total Remaining Time: | n.a. | Estimated Remaining Time: | n.a. |
Description (last modified by jmoore)
Model objects have a new serialVersionUID generated on every build. This obviously breaks lots of things.
Change History (5)
comment:1 Changed 18 years ago by jmoore
comment:2 Changed 18 years ago by jmoore
- Keywords iteration4 added
- Milestone changed from Unscheduled to 3.0-M3
- Priority changed from minor to critical
- Summary changed from Add tests to test changes in model serialization to Fix serialization and add tests for model changes
comment:3 Changed 18 years ago by jmoore
- Status changed from new to assigned
Finally bit the bullet and changed this. r888 sets a single, static value for the serialVersionUID of all our generated model objects. When changes are made to the model that break serialization, this value will need to be updated to prevent weird exceptions.
The tests are still needed, but we can reschedule those for later.
comment:4 Changed 18 years ago by jmoore
r889 removes the spurious serialVersionUID.
comment:5 Changed 18 years ago by jmoore
- Description modified (diff)
- Priority changed from critical to blocker
- Resolution set to fixed
- Status changed from assigned to closed
- Summary changed from Fix serialization and add tests for model changes to Fix model serialization
r823 begins work on fixing model object serialization. Now SemanticType and mapping.vm work together to produce a single serialVersionId for all model classes. This means that classes are reusable over different compiles. (Not yet over different code generations. A property will need to be added to the build for that.)