Spring WS - Part 3

Now let's go into little details of the whole App
So from the Client Controller, we invoke the service with the help of WebServiceTemplate after contructing appropiate request model. The configuration for WebServiceTemplate can be found in SpringWSApplicationConfig.java. It can be seen that in the request model we are attaching a file. We have used MTOM here for the attachment purpose, which we will discuss in detail in upcoming posts.

So the requuest before reaching the specified endping, which is being determined by EndpintMapping implementation passes through a series of interceptors configured in SpringWSApplicationConfig.java in addInterceptors bean.

I have used here two Spring WS in-built interceptors:
1) SoapEnvelopeLoggingInterceptor.java
2) PayloadLoggingInterceptor.java
 They are basically logging interceptors and one Custom interceptor i.e. CountryInterceptor.java
The code for Custom interceptor is already provided above.
Now to use Custom interceptor we need to wrap in into PayloadRootSmartSoapEndpointInterceptor. We can also specify the namespace and the payload of the request for which the interceptor would get invoked just the same as we can do from Service endpoint with the help of @PayloadRoot annotation.

So after the interceptors has finished processing, anf if there is no problem (true is returned from the method) then the request would go to Service endpoint, had there been any problem (false is returned from the method), then the request wont reach the service endpoint.

Once the request reaches the service endpoint based on the namespace and the payload of the request, the appropiate method is invoked and response is retuned back to the client. Had there been any exception, as described in the above Service Endpoint code, then SOAP fault is returned. Please note we cannot declare two methods within the Service Endpoint having identical namespace and the payload, as in this case there would be exception during startup.

Fault Handling in Spring WS can be configured with the help of Exception Resolvers
. We will also see to it :-)

MTOM with Spring WS

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