Activity for steph96
-
steph96 posted a comment on ticket #185
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
-
C.77 OperationInvokedReportPart and multi-state updates
-
MdState/@StateVersion not incremented for added and removed context states
-
wse:Identifier is not usable
-
Add info in which cases wsa soap header fields can be omitted
-
WS-Addressing usage in SOAP messages is not well defined in all cases, if I understand correctly. For UDP (WS-Discovery) messages, it is clear that WS-Addressing 1.0 has to be used for all messages The SOAP envelope MUST use the mechanisms defined in WS-Addressing [WS-Addressing]. (See section 2.2 of Soap-over-UDP 1.1) For SOAP messages over HTTP it is not completly defined. DPWS 1.1 specifies in section 2.5 R5005: A SERVICE MUST at least support WS-Addressing 1.0 DPWS indicates, that it is allowed...
-
Currently, there is no source for "old"/previous sequenceid/instanceid information. It is only available, in case the client has seen the device before with that MDIB version group information.
-
What does "type Update" mean? Are (1) descriptor updates still allowed in the report but only the descriptor type (coded value) is not allowed to change, or (2) are all updates of descriptors disallowed?
-
SystemContext (descriptor) shall be optional in MDS
-
ModifiableElement in AbstractOperationDescriptor not clearly documented
-
unknown null flavor in InstanceIdentifier
-
unknown null flavor in InstanceIdentifier
-
xsd:duration documentation
-
StateRevision in GetStatesFromArchive should be optional
-
WaveformStream should be derived from AbstractReport
-
Clarify leap seconds usage in Timestamp
-
Rename measure to measurement
-
Fix explanation of Medical Device Containment Tree
-
Define the term SOMDA
-
Are instantiation of AbstractStates allowed
-
Limit scope of handles in GetContextState
-
Add Extension Interpretation element
-
Format R0084 as requirement
-
Add documentation that StateVersion can omitted if it is the default value
-
AbstractMetricValue and MeasurementState
-
Set MeasureValue to required in Measurement
-
Set MeasureValue to required in Measurement
-
MeasurementPeriod vs update period
-
MeasurementPeriod vs update period
-
Rename measure to measurement
-
InvocationError: Difference between UNSPECIFIED and OTHER
-
Clarify why there may be no VMD in HydraMDS
-
Clarify the behavior of an alertsystem if MonitoredAlertLimits is set to ALL_OFF
-
Add state diagram for ComponentActivationState
-
R0079: define an identifier
-
It is not defined, that "biceps:" is a XML namespace prefix. In case of using another...
-
Update documentation of ClockDescriptor/TimeProtocol
-
Add documentation for "overflow"/"underflow"
-
Change heading of chapter 6
-
Enhance documentation of ModifiableElement
-
Enhance OperationTarget documentation in XML Schema
-
Enhance documentation for MaxDelayTime
-
Remove Activation enum
-
Update CodeId documentation
-
Clarify alert vs alarm usage.
-
Add documentation for ProductionSpecification
-
Change cardinality of SystemMetaData/ModelNumber
-
Avoid duplicate Requirement number R0010
-
Fix explanation of Medical Device Containment Tree
-
The wording "consists of at least one" suggest, that it is possible to have more...
-
If the model supports more than one SCO, we should remove the SCO concept completely....
-
SCO ist NOT a device component. It does not have a ProductionSpecification. It is...
-
Enhance OperationTarget documentation in XML Schema
-
Enhance documentation of ModifiableElement
-
Resolution shall be optional
-
Change Timestamp base data type to xsd:decimal
-
Change Timestamp base data type to xsd:decimal
-
Change MAX_UDP_ENVELOPE_SIZE to MAX_LARGE_UDP_ENVELOPE_SIZE
-
There is still a StateVersion counter missing (MDState)
-
Enhance documentation of StateVersion & DescriptorVersion
-
Change SystemMetaData/UDI from uri to string
-
Clarify LocaleInfo of AbstractMDSState
-
Fix documentation of SystemContext\WorkflowContext
-
Fix Documentation for AlertSignalManifestation\Visible &Tangible
-
Change attribute AlertSignalDescriptor/IsSignalDelegationSupported to AlertSignalDescriptor/​SignalDelegationSupported
-
Change attribute LimitAlertConditionDescriptor/IsAutoLimitSupported to AutoLimitSupported
-
Clarify the documentation of PausableActivation & LatchablePausableActivation
-
Change order of rank and degradationprio in AlertConditionState
-
Change documentation for AlertSignalState\Location
-
Clarify the behavior of an alertsystem regarding AlertSignal\Slot
-
Change SelfCheckTime to LastSelfCheck
-
Change SelfCheckCnt to SelfCheckCount
-
VersionCounterRef is not used as a reference. A Reference is a pointer to another...
-
safety transmission of metric (one-way)
-
OperationInvokedReports are for the client of the Set request only
-
OperationInvokedReports are not always used
-
InvocationError: Difference between UNSPECIFIED and OTHER
-
Including information about daylightsaving time changes? The timezone changes at...
-
Remove AbsoluteTime data type
-
Improve description of Instance Identifier
-
MDIB versioning
-
qualified attributes
-
MDIB versioning
-
HTTPBinding constructor registers itself before it is build up
-
In a few places it is still named JMEDSFramework instead of CoreFramework. See attached...
-
wsa:From support
-
I do not know what the intention of the programmer is, but as far as I understand,...
-
My device hangs in an endless loop. } else if (PROP_TYPES.equals(property.key)) {...
-
Hello, I using beta 9 and get the following error: No OutgoingDiscoveryInfos, no...
-
Hi Jannis, I downloaded the sources of JMEDS. Since there is no XML pull parser included,...
-
I am using the JMEDS beta10 sources and the following import appears in SerializeUtil.java:...
-
What do you mean by "rev 788". When I browse the code, the last rev is 119 https://sourceforge.net/p/ws4d-javame/code/...
1 >
