A way of sending a message to invoke an operation on another computer. The difference between web services and previous methods is what gets sent over the wire is standardized at a higher level.
Continue reading What is a “web service” in plain English?
The TL;DR version: JAX-WS is meant for XML based web services such as SOAP. JAX-RS does not have the same restriction.
JAX-WS is generally geared towards server to server interactions with well defined contracts (WSDLs) and usually when the service and client side are from separate groups. It is very resource intensive so it isn’t feasible for client-to-server interactions where the network or client device capability is less than optimal.
JAX-RS is geared towards client to server interactions, although server-to-server is okay. As it has little service obligations, it can be tuned to whatever the client needs are.
Continue reading JAX-WS vs JAX-RS
When developing using web services, we tend have different endpoint URLs for development, test and production. When developing Java EE apps, the best practice is to separate environment configuration from the application to the deployment process (a pattern I rarely see in practice unless already architected in like Curam).
In terms of facepalm moments is when I see an application try to manage the connections to the web services rather than letting the container do it.
Continue reading Setting the endpoint for web services
Doing webservices in Curam is quite easy now that they are using Axis 1.2 which can parse more WSDL files. It is not the latest yet, but so far the WSDLs that are generated for a .Net environment do work in Java. I never bothered with the .cat file generation, I don’t think it works too well especially with complex WSDLs. Fortunately, we do not need them.
Continue reading Getting webservices working in Curam development