Name clash possible for cross-extension scenario

Submitted by Josef Kaltwasser on Monday, 26 March, 2012 - 15:46
Issue ID
83
Component
Methodology
Category
Bug report
Priority
Normal
Assigned
Status
Fixed
Source
ES5
Description

The following can happen:
A client is developed against a level B extension "X". It connects to a server that has been developed against another level B extension "Y". In the case where extensions X and Y both contain a level B extensions class (i.e. a class with a tagged value named "extension" and set to "levelb") with the same name, the client will misinterprete the extension content with unpredictible result.

Proposal:
Add a unique element (e.g. UUID) to the name of levelB extensions classes, i.e. all classes with a tagged value named "extension" and set to "levelb".

{"changeLogs":[{"date":1528111213281,"statusOLD":"- None -","status":"Fixed","priorityOLD":"- None -","priority":"Normal","categoryOLD":"- Select a value -","category":"Bug report","componentOLD":"- Select a value -","component":"Tool","assignedOLD":"","assigned":"Josef Kaltwasser (18)"},{"date":1528119230014,"componentOLD":"Tool","component":"Methodology"},{"date":1537269680122}]}

Posted by Josef Kaltwasser on July 15, 2020 Permalink

No longer an issue since the introduction of namespaces.