One of our partner has requested to provide full featured REST APIs so that almost new UI can be created by accessing those APIs.
To support this, we need very big changes internally.
It's because current perftest highly depends on the field definition step and initial value provided by the ngrinder UI.
If a REST API user misses to set up some fields in the perftest, perftest can be easily uncontrollable.
Therefore, followings should be addressed to make it work in REST API.
1. Current entity merge scheme should be changed to support any field having null can be ignored. This makes the each entity easily filled progressively.
2. Avoid the initial value in the entity classes. Instead, provide explicit entity initialization step just before saving to JPA. This makes each entity can be bounded to REST API parameter in controller.