Uploaded image for project: 'HPCC'
  1. HPCC
  2. HPCC-20354

improve DESDL service name handling


    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 7.0.0
    • Component/s: DESDL, ESP
    • Labels:


      I setup a DESDL template service and binding in configmgr. I published ecm content and created a binding in ECL Watch. The service name I entered in the binding matched the ESP binding name, which did not match the ESDL service name.

      ECL Watch was able to see and edit the defined methods.

      The ESDL service binding did not see the defined methods. In the form view, it presented an empty DESDL service with the name of the binding. After editing a method definition in ECL Watch, refreshing the form view resulted in the empty DESDL service followed the expected ESDL service name and methods.

      Replacing the binding with the one whose name matched the ESDL service name, the ESDL service binding properly loaded the service when refreshed.

      If the binding service name can be entered by the user, it should not be expected to match the ESDL service name. If a match is expected, is a user defined binding name necessary or should the ESP take the name it wants from the ESDL definition?




            • Assignee:
              mayx Yanrui Ma
              klemti01 Tim Klemm
            • Votes:
              0 Vote for this issue
              3 Start watching this issue


              • Created: