Topic rendering fails if cardinality has changed meanwhile
Example: assume 1234 is a composite topic with a cardinality "One" assoc def.
- Clear the browser cache.
- Select that topic. The webclient sends a
GET /core/topic/1234
request. - Change assoc def's cardinality to "Many".
- Select the topic again. The webclient sends a
GET /core/topic/1234
request again. This time the server responds with304 Not Modified
and the webclient uses the cached topic JSON. Rendering fails as the topic's JSON is not compatible with the type definition anymore. ("Many" child topics are formatted as a JSON array; a "One" child topic is formatted as a JSON object.)
The DM4 Webclient has the same problem.
@mukil: FYI