Spring Web Services

Recently I was trying to explore Web Services using Spring i.e. Spring WS. So I went through the official documentation of Spring WS and after traversing it a bit I found it quite easy to configure and the concept of Contract First Web Services makes it more interesting keeping in mind all the real time situations.

So I decided to prepare a demo application to get an idea about its various features and believe me starting from configuring to testing my first Spring-based web services was really cool except in some places where I got stuck like the endpoint url for invoking the Web Services as the service endpoint url for invoking the web services and the one present in the generated WSDL are not identical, so I had a little hard time in figuring the right endpoint url for invoking the service. The WSDL generated here from a xsd with the help of a Spring injected (in Configuration File SpringWSApplicationConfig.java) bean seems to me more of a request response format for a particular web service, Please let me know me if I am not correct :-)...

So, in this tutorial I am going to share my experience with Spring Web Services. I will not be going into the details of all the annotations and the description of various components of SpringWS as those elements are covered in a comprehensive manner in the official documentation site. I will mainly be concentrating on various basic configurations required to startup a very basic web service and some other interesting and useful features. I have used here java based configuration instead of xml based.

spring-ws-part-1

Comments

Post a Comment

Popular posts from this blog

Use of @Configurable annotation.

Not, all types(beans) used in a Spring Based Application are Spring managed. Sometimes, we need to inject some dependency into some Types which are not Spring Managed. The most common example being, injection of Service or DAO layer within the Entity class. Now the instances of Entity classes are being created using the new operator, i.e. they are not Spring Managed. Now we want to inject the corresponding Service or DAO Type which is Spring Managed within these Entity Types, and these can be performed with the help of @Configurable . It is the Aspects, which performs all the underlying engineering and ,makes this thing possible. Let's see an example. @Configurable public class Person { @Autowired ResourceBundleThemeSource themeSource; private String firstName; private String lastName; private int age; private Address address; @CustomDateFormat Date birthDate; MultipartFile profile; public String getFirstName() { return firstName; } public voi
Read more

Spring WS - Part 5

Spring WS provides an easy integration with various WS-Security features with the help of interceptors like Wss4jSecurityInterceptor, XwsjSecurityInterceptor. We are going to explore here very basic feature of WS-SECURITY i.e. implementing Security using with UserNameTokenAuthentication We are going to use Wss4jSecurityInterceptor as it is very easy to configure. We are going to use configure two interceptors: 1) One for the Server End. 2) Other for the Client End. For Server End The configuration for Wss4jSecurityInterceptor is as follows: @Bean public Wss4jSecurityInterceptor wss4jSecurityInterceptor() { /** * The SecurementActions for UsernameToken is commented, as the * UsernameToken is to be added by the client, the server-side * interceptor would only validate that. * */ Wss4jSecurityInterceptor wss4jSecurityInterceptor = new Wss4jSecurityInterceptor(); wss4jSecurityInterceptor.setValidationActions("UsernameToken");
Read more

Spring WS - Part 4

Another interesting and essential feature is the attachment part. Now I found two things out here. The attachment can be inline within the SOAP message body (suitable as long as the attachment size is not too long) or we can enable MTOM feature within the marshaller and leverage the MTOM-XOP feature. For the attachment to be inline with the SOAP message body, no actual configuration are required, everything is being taken care by the Spring WS framework, except the following: &ltxs:element name="getCountryRequest"&gt &ltxs:complexType&gt &ltxs:sequence&gt &ltxs:element name="name" type="xs:string"/&gt &ltxs:element name="file" type="xs:base64Binary" xmime:expectedContentTypes="application/octet-stream"&gt&lt/xs:element&gt &lt/xs:sequence&gt &lt/xs:complexType&gt &lt/xs:e
Read more