Design thoughts on a schema based request object for CXF endpoint
Trying to seek design suggestion on a schema based request object for a CXF endpoint. I’ve created a CXF SOAP endpoint which takes the following object as an input. The request object will have required fields, non-mandatory fields as well as user-defined fields.Required fields are enforced through the schema. The tag object is defined as a placeholder for user defined properties. The eventual goal of the endpoint has transformed the values into Tag object and send them for processing.
AGPL License – does it apply in this scenario?
There is an AGPLv3 based software (Client) that makes web service calls (using SOAP) to another software (Server – commercial, cloud based). There is no common code or any connection whatsoever between these two except for the web service calls being made.
What is the difference between SOAP and Web Services?
Keep getting confused about these two. Anyone care to explain the difference(s)?
In developing a soap client proxy, which return structure is easier to use and more sensible?
I’m writing (in PHP) a client/proxy for a SOAP web service. The return types are consistently wrapped in response objects that contain the return values. In many cases this make a lot of sense – for instance when multiple values are being returned:
How does signing headers and/or body provide security
I’m securing a WCF webservice with TransportWithMessageCredential security that uses certificates.
So I’ll have to choosee between signing headers & body or signing and encrypting.
How does signing headers and/or body provide security
I’m securing a WCF webservice with TransportWithMessageCredential security that uses certificates.
So I’ll have to choosee between signing headers & body or signing and encrypting.
How does signing headers and/or body provide security
I’m securing a WCF webservice with TransportWithMessageCredential security that uses certificates.
So I’ll have to choosee between signing headers & body or signing and encrypting.
How does signing headers and/or body provide security
I’m securing a WCF webservice with TransportWithMessageCredential security that uses certificates.
So I’ll have to choosee between signing headers & body or signing and encrypting.
Can a webservice that uses JSON over POST be classified as RESTful?
Recently I have started using a new(to me) paradigm for web services. I use the controller to accept JSON strings sent over POST, process it and return JSON strings. GET, PUT, DELETE and other methods throw HTTP 405.
Can a webservice that uses JSON over POST be classified as RESTful?
Recently I have started using a new(to me) paradigm for web services. I use the controller to accept JSON strings sent over POST, process it and return JSON strings. GET, PUT, DELETE and other methods throw HTTP 405.