Hello Christian, last week I have uploaded a new build which will not expire. Best wishes Ingo
Hello Bence, I also wish you a happy new year! The Explorer I have uploaded last week will not expire. So unfortunately, this long tradition will end this year ;-) Best wishes Ingo
Time goes so fast. Yet another year over. … and I did it again! Best wishes Ingo
Hello Andreas, sorry for the delay but I had no time to try it out earlier. I tested the example with our explorer 4. There was no problem invoking the operations of the “GetService” (GetMdDescription, GetMdState and GetMdib). I invoked each of them without an input parameter and the responses were processed without any issue. But the wsdl delivered by the “BicepsService” is not correct and caused an error. There is the following element quite at the end of the wsdl: <mdpws:streamtype id="WaveformStream"...
Happy new year Martin. I’ll do my very best! It is updated now. Best wishes Ingo
Hi Martin, happy new year 2019! The DPWS Explorer on ws4d.org is extended now. Best wishes Ingo
Hello Guilherme, we are still working on JMEDS. Among other things, we are currently reimplementing the internal representation of WSDL and XML Schema data structures and the functionality around it. Furthermore we will drop the old Java ME support which limits the usable language features. In this context we will for example improve the API with generics. We assume to release the new version in the second half of 2018. Support for users is provided by means of the forum- and ticket-system on Sourceforge....
Hello together, a new version (3.13.9) of the explorer has been uploaded to ws4d.org. Sorry for the delay. Best wishes and a happy new year Ingo
Hello David, due to some vacation we will not be able to start examining this issue...
Hello Martin, it is generally possible to use the SOAPoverUDPClient and SOAPoverUDPServer...
Hello Martin, I’m sorry, but it is currently no possible to have attribute names...
Hi Sebastian, I fixed this bug by the following change in DefaultClient (in the line...
Hi Martin, DeviceReferences that do not have at least one DeviceListener are automatically...