I am trying to use the auto-generated wsdl to create a dynamic client. However, whenver I try to do that I always receive an error. I am using SoapUI tool to create requests. I imported the wsdl and everything seems ok. However, if I execute the request I always receive the HTTP 404 error. I attach the request, a printscreen with device info showed in the DPWS explorer, and the wsdl (generatedby JMDS).
Hi Giovanni,
your problem seems to be, that your client does not support eventing. not request-response or one-way is correct. ResourceCommSimpleEvent is a notification, because it only has an output message.
The other warnings are probably related to this problem.
BR,
Chris
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Also, the ReadData invoke message in your SoapUITest cannot be a valid request. The content-length: 122 indicates, that the message is too short. The HTTP 404 error is a little bit misleading, though :D
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
thank you for the help. Maybe I have not configured properly the SoapUI tool. I have only added the WSDL and tried to invoke the readData operation. By the way, I am trying to use the JMEDS framework to implement an edge-based architecture for reading and analysing data. JMEDS seems good option to do that however I need to keep the devices free from any api and/or library, i.e. in REST we only need an URL to access the device, so any external application only need the url to create an http client and get data. For this reason, I want to be sure that an external application could potentially communicate with my devices by using the wsdl. Are you able to replicate the test (with a wethever device)? Furthermore, I aslo tried with wsimport from java to create the client and invoke the operation and it didn't work. Do you have any comment and/or suggestion?
Thank you in advance for the help.
Cheers,
Giovanni
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I am trying to use the auto-generated wsdl to create a dynamic client. However, whenver I try to do that I always receive an error. I am using SoapUI tool to create requests. I imported the wsdl and everything seems ok. However, if I execute the request I always receive the HTTP 404 error. I attach the request, a printscreen with device info showed in the DPWS explorer, and the wsdl (generatedby JMDS).
Do you have any suggestion?
Thank you.
Cheers,
Giovanni
Last edit: Giovanni Di Orio 2016-12-17
Moreover, if I try to generate the client by using wsimport (retrieving the wsdl from the link into the explorer http://10.0.2.15:50779/eu/dpws/jmeds/adira/Mantis_Dummy_Device/DataExtractionService/ws4d/resources/mantis.eu/dpws/jmeds/adira/Mantis_Dummy_Device/description.wsdl) I have the following warnings:
[WARNING] SOAP port "DataExtractionServiceEventsPort0": uses a non-standard SOAP 1.2 binding.
line 5 of http://10.0.2.15:50779/eu/dpws/jmeds/adira/Mantis_Dummy_Device/DataExtractionService/ws4d/resources/mantis.eu/dpws/jmeds/adira/Mantis_Dummy_Device/description.wsdl
[WARNING] ignoring operation "ResourceCommSimpleEvent": not request-response or one-way
line 5 of http://10.0.2.15:50779/eu/dpws/jmeds/adira/Mantis_Dummy_Device/DataExtractionService/ws4d/resources/mantis.eu/dpws/jmeds/adira/Mantis_Dummy_Device/description.wsdl
[WARNING] Port "DataExtractionServiceEventsPort0" does not contain any usable operations
line 5 of http://10.0.2.15:50779/eu/dpws/jmeds/adira/Mantis_Dummy_Device/DataExtractionService/ws4d/resources/mantis.eu/dpws/jmeds/adira/Mantis_Dummy_Device/description.wsdl
[WARNING] SOAP port "DataExtractionServicePort0": uses a non-standard SOAP 1.2 binding.
line 5 of http://10.0.2.15:50779/eu/dpws/jmeds/adira/Mantis_Dummy_Device/DataExtractionService/ws4d/resources/mantis.eu/dpws/jmeds/adira/Mantis_Dummy_Device/description.wsdl
BR,
Giovanni
Hi Giovanni,
your problem seems to be, that your client does not support eventing.
not request-response or one-wayis correct.ResourceCommSimpleEventis a notification, because it only has an output message.The other warnings are probably related to this problem.
BR,
Chris
Also, the
ReadDatainvoke message in yourSoapUITestcannot be a valid request. Thecontent-length: 122indicates, that the message is too short. TheHTTP 404error is a little bit misleading, though :DDear Chris,
thank you for the help. Maybe I have not configured properly the SoapUI tool. I have only added the WSDL and tried to invoke the readData operation. By the way, I am trying to use the JMEDS framework to implement an edge-based architecture for reading and analysing data. JMEDS seems good option to do that however I need to keep the devices free from any api and/or library, i.e. in REST we only need an URL to access the device, so any external application only need the url to create an http client and get data. For this reason, I want to be sure that an external application could potentially communicate with my devices by using the wsdl. Are you able to replicate the test (with a wethever device)? Furthermore, I aslo tried with wsimport from java to create the client and invoke the operation and it didn't work. Do you have any comment and/or suggestion?
Thank you in advance for the help.
Cheers,
Giovanni