myService MyServicePart{@dedicatedService};
In that declaration, you must specify the Service part, not an Interface part.
After declaring the variable, you use it in a call statement, as described in “Invoking a service asynchronously from a Rich UI application.”
After you declare the variable and assign a service binding to it, you use the variable in a service-access statement, as described in “Invoking a service synchronously from outside of Rich UI.”
When you are accessing a local EGL service outside of Rich UI, you can base the service-access variable on an Interface part. The part includes function prototypes that match some or all of the functions in the Service part.
Interface MyInterfacePart
Function GetEmployeeDetail(employeeCode STRING IN,
employeeSalary FLOAT OUT,
employeeStatus STRING INOUT)
returns(myEmployeeRecordPart);
end
The example includes a single function prototype, but more are possible. Also, you can specify a variety of EGL data types and can use the modifiers IN, OUT, and INOUT.
When accessing a non-SOAP service, avoid a possible runtime error: do not use an Interface part that is derived from a WSDL file.
When you are working outside of Rich UI and are accessing a local EGL service, you must set the service binding in the EGL deployment descriptor. The rule applies whether you use a Service or Interface part as the basis of the service-access variable.
myService MyInterfacePart {@BindService{bindingKey="MyInterfacePart"}};
MyService MyInterfacePart {@BindService};
For details on assigning or reassigning the service binding at run time, see “Binding a service-access variable dynamically.”