steph96

The generated soapC.cpp has also a timestamp in it. It is in the source code and thus leads to trouble with ccache in our environment. See https://sourceforge.net/p/gsoap2/code/HEAD/tree/gsoap/samples/calc_xcode/soapC.cpp#l21 for example where SOAP_SOURCE_STAMP("@(#) soapC.cpp ver 2.8.135 2024-07-01 20:02:42 GMT") is written to the cpp file. Please also replace the timestamp there. The provided path is only for the wsdl2h executable not for soapcpp2. Please add support to soapcpp2 also. Thanks.

My conclusion from what I understand: The report part operation target is only relevant for create and to avoid any trouble in that case only one state creation is allowed at a time. In all other cases the content of the report part operation target should be ignored.

SOAP 1.2 uses XML infoset for its messages. XML Infoset has order ("An ordered list of child information items, in document order.") Furthermore XML infoset says "This specification describes the information set resulting from parsing an XML document. " leads to the conclusion that the order of XML elements is important and an XML processort is NOT allowed to reorder.

Is it allowed to have a SSA entry for Manifestation="Tan" in case there is no tangible alert signal in the alert system? Is it allowed to be in any state On, Psd, or Off?

C.77 OperationInvokedReportPart and multi-state updates

B.440 MeasurementValidity

B.128 SystemSignalActivation event/duration requirement

B.128 Multiple SystemSignalActivation with same Manifestation