Qualifier mapping generates redundant XML elements

Submitted by Josef Kaltwasser on Wednesday, 19 May, 2010 - 17:34
Issue ID
11
Component
Methodology
Category
Feature request
Priority
Normal
Assigned
jaderberg
Status
By design
Source
Website
Description

It is awkward that the mapping of UML qualifiers generates two redundant, nested XML elements of the same name.
Example:
                    <measurementSpecificCharacteristics index="0">
                        <measurementSpecificCharacteristics>
                            <accuracy>10</accuracy>
                            <specificLane>lane1</specificLane>
                            <specificMeasurementValueType>trafficSpeed</specificMeasurementValueType>
                            <specificVehicleCharacteristics>
                                <vehicleType>motorcycle</vehicleType>
                                <vehicleType>car</vehicleType>
                                <vehicleType>van</vehicleType>                               
                            </specificVehicleCharacteristics>
                        </measurementSpecificCharacteristics>
                    </measurementSpecificCharacteristics>

The mapping should generate only one element instead.

{"changeLogs":[{"date":1528113550397,"assignedOLD":"","assigned":"jaderberg (22)","statusOLD":"- None -","status":"By design","priorityOLD":"- None -","priority":"Normal","categoryOLD":"- Select a value -","category":"Feature request","componentOLD":"- Select a value -","component":"Methodology"},{"date":1537270890136}]}

Posted by Joerg Freudenstein on May 10, 2036 Permalink

Probaly a Tool Problem; but need to do further research.

Posted by Josef Kaltwasser on March 10, 2034 Permalink

The two layers are actually needed since the inner layer carried the type of the data structure whereas the out layer carried the index attribute that counts the occurrences