Behaviour change for SOAP clients in Uniface 10.3
Author: firstname.lastname@example.org (Adrian Gosbell)
A reminder that with effect from Uniface 10.3, any component-level operation or exec operation of a Service component or Static Server Page has to be declared as public for it to be activated from a SOAP request. (Dynamic Server Pages have already required this). From Uniface 9.7.04+G402 is was optional, with Uniface 10.3, it's required. Pasted from the Uniface 10.3 documentation:
Declares that the operation can be activated by a SOAP request.
UseUse in the declaration of the component-level operation or exec operation of a Service component, Dynamic Server Page, or Static Server Page.
DescriptionThe public soap declaration can be used to make an operation accessible to the SOAP client. If a SOAP client attempts to activate an operation that does not contain the public soap declaration, a
Making Operations Accessible to SOAP Clients
operation SOAP_UPDATE public soap ;- declare accessible via SOAP channel params endparams <... do something ...> end
Making a DSP Operation Accessible to Both Web and SOAP ClientsIt is possible to use both the public soap and public web declarations in a DSP operation or trigger.
operation doSomething public soap public web scope input output endscope < ... do something ...> end