Comet system forum
Discussion forum about Comet system products
Temperature, Humdity,
Pressure Transmitters
and Data Loggers
You are not logged in.
#1 04-12-2013 11:18:06
- TGarabedyan
- Member
- From: Bulgaria
- Registered: 31-03-2009
- Posts: 7
- Website
SOAP backward compatibility for Tx5xx
Is it possible to customize SOAP envelope as it was prior firmware 1.5.6?
As I see the SDK is no more available for download, so the old WebFileCreator v1 is not intended to be used for recent firmwares.
This create backward incompatibility with previous devices, when soap file could be changed according customer's need.
I could extend my SOAP server (custom developed for GlassFish), but it will require additional efforts for upgrade all my 20 sensors to recent firmware.
Offline
#2 04-12-2013 12:57:21
- HonzaD
- Administrator
- Registered: 11-08-2008
- Posts: 294
Re: SOAP backward compatibility for Tx5xx
Hi,
Please check your mailbox. I can help you change SOAP messages format.
Jan
Offline
#3 05-12-2013 09:24:40
- TGarabedyan
- Member
- From: Bulgaria
- Registered: 31-03-2009
- Posts: 7
- Website
Re: SOAP backward compatibility for Tx5xx
Yesterday I tought that I overcome with the SOAP problem, but obviously not.
The detailed debug of new SOAP message (when come from 1.5.5 firmware device) missing "javax.xml.ws.wsdl.operation" value.
In the previous schema it was correctly set to "InsertSample".
Now the HTTP context parameter "javax.xml.ws.http.request.headers" contain soapAction, but the value is set to "http://cometsystem.cz/schemas/soapTx5xx_v2.xsd/InsertTx5xxSample", not just "InsertTx5xxSample".
Some articles suggest to add soapAction attribute to soap:operation node in WSDL.
How to solve this?
Offline
#4 05-12-2013 11:23:58
- HonzaD
- Administrator
- Registered: 11-08-2008
- Posts: 294
Re: SOAP backward compatibility for Tx5xx
Hi,
As I know, previous SOAP implementation with only "InsertSample" was improper. We added "http://..../soapTx5xx_v2.xsd/InsertTx5xxSample" for compatibility with IIS. I really think that implemtation is now correct.
But if you need change SOAPaction header, it is not a big problem. Just email to me what SOAPAction header and SOAP message you need and I can change this for you.
Jan
Offline
#5 05-12-2013 15:55:11
- TGarabedyan
- Member
- From: Bulgaria
- Registered: 31-03-2009
- Posts: 7
- Website
Re: SOAP backward compatibility for Tx5xx
IIS has diferent Provider Factory than GlassFish and Apache (Tomcat).
In order for the new SOAP implementation to work on Java-based Web Services, it must be able to return in SOAPMessageContext under
"javax.xml.ws.wsdl.operation" => {...}InsertTx5xxSample value.
Offline
#6 06-12-2013 07:06:19
- HonzaD
- Administrator
- Registered: 11-08-2008
- Posts: 294
Re: SOAP backward compatibility for Tx5xx
Hi,
As I wrote in previous post. If you need change SOAP message format, just send to me required SOAPAction header and SOAP message format and I change this for you.
Jan
Offline