Think about purchase as a business entity or a resource in RESTful dictionary. That being said, making a purchase is actually creating a new resource. So: POST /api/purchase will place a new order. The details (user, car, etc.) should be referenced by id (or URI) inside the contents sent to this address. It doesn’t matter … Read more
A web service typically offers a WSDL from which you can create client stubs automatically. Web Services are based on the SOAP protocol. ASP.NET Web API is a newer Microsoft framework which helps you to build REST based interfaces. The response can be either JSON or XML, but there is no way to generate clients … Read more
You don’t need a third party library to use jax-ws annotations. J2SE ships with jax-ws, so all the annotations are still available to you. You can achieve lightweight results with the following solution, but for anything optimized/multi-threaded, it’s on your own head to implement: Design a SEI, service endpoint interface, which is basically a java … Read more
Yes, your observation of the behavior is accurate. Internet Explorer 10 and below follow a complicated algorithm for encoding the URL. This was allegedly updated in Internet Explorer 11, but I’ve found that the new option doesn’t seem to work. The “Always show encoded addresses option” concerns whether PunyCode is shown for IDN hostnames, and … Read more
So, it looks like I’ve found possible answer while combining JAX-WS & JAXB related answers from SO (I would really appreciate if somebody experienced in these technologies can check whether following is correct): The obvious thing for me is to add SOAP message handler and alter header of SOAPMessage instance in it: import javax.xml.ws.Binding; import … Read more
You could use a combination of JQuery with JSON calls to consume REST services from the client or if you need to interact with the REST services from the ASP layer you can use MSXML2.ServerXMLHTTP like: Set HttpReq = Server.CreateObject(“MSXML2.ServerXMLHTTP”) HttpReq.open “GET”, “Rest_URI”, False HttpReq.send
Had this problem when upgrading from CXF 2.3.x to 2.7.x Added stax2-api and woodstox-core-asl jars from the 2.7.x CXF distribution and the webservice works again.
With a good RESTful service, it’s not necessary to generate WADL (let alone the much-less-well-fitting WSDL) for it because it will self-describe. By “self-describe” I specifically mean that it will deliver documents describing all the (relevant) resources published by the service, and that using a standard HTTP OPTIONS request on any of these will produce … Read more
You can bind in a schema to the log4net element. There are a few floating around, most do not fully provide for the various options available. I created the following xsd to provide as much verification as possible: http://csharptest.net/downloads/schema/log4net.xsd You can bind it into the xml easily by modifying the log4net element: <log4net xsi:noNamespaceSchemaLocation=”http://csharptest.net/downloads/schema/log4net.xsd” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”>
There’s another, very secure method. It’s client certificates. Know how servers present an SSL Cert when you contact them on https? Well servers can request a cert from a client so they know the client is who they say they are. Clients generate certs and give them to you over a secure channel (like coming … Read more