Ticket #253 (closed Defect: fixed)
After the fact invalidation of an association definition through role type change corrupts the database! Server restart doesn't help!
| Reported by: | jri | Owned by: | jri |
|---|---|---|---|
| Priority: | Blocker | Milestone: | Release 4.1 |
| Component: | DeepaMehta Standard Distribution | Version: | 4.0.10 |
| Keywords: | Cc: | ||
| Complexity: | 3 | Area: | |
| Module: | deepamehta-core |
Description (last modified by jri) (diff)
This occurs if you have a valid association definition (e.g. "Composition Definition") and then invalidate it by a role type change (e.g. typing "Whole Type" to "Default"). Now when you restart the server it throws an exception and the client is not usable.
A server restart doesn't help.
This is a mega blocker.
Change History
comment:3 Changed 13 years ago by jri
Core fix: catch invalid association defs (#253).
The webclient doesn't break anymore under the condition decribed in #253.
However, the fix is not complete yet: once the user has repaired the assoc def it is not active before she performs one extra step: retype the association, and then retype it back to the desired association type.
Changeset: 0ab084afae08597dea306146fd5c67394e2c61ec (May 15)
comment:4 Changed 13 years ago by jri
The original issue is fixed.
The issue mentioned in the previous comment could be addressed in a separate ticket.
comment:5 Changed 13 years ago by jri
- Status changed from accepted to closed
- Resolution set to fixed
comment:6 Changed 13 years ago by Jörg Richter
Core fix: catch invalid association defs (#253).
The webclient doesn't break anymore under the condition decribed in #253.
However, the fix is not complete yet: once the user has repaired the assoc def it is not active before she performs one extra step: retype the association, and then retype it back to the desired association type.
See ticket 253.
