The post explains different ways of retrieving header parameters in JAX-RS annotated method. Below is the complete code 1 package resource; 2 3 import javax.ws.rs.GET; 4 import javax.ws.rs.HeaderParam; 5 import javax.ws.rs.Path; 6 import javax.ws.rs.core.Context; 7 import javax.ws.rs.core.HttpHeaders; 8 import javax.ws.rs.core.MediaType; 9 import javax.ws.rs.core.Response; 10 11 @Path(“webresource3”) 12 public class WebResource3 { 13 @GET 14 @Path(“headerParameters1”)…… Continue reading Retrieving header parameters in JAX-RS annotated method
Creating dependent tasks
In this post of gradle, I will show two different ways to make one task depend upon other. build.gradle 1 task task1 { 2 doFirst { 3 println ‘I am dependee’ 4 } 5 } 6 7 task task2(dependsOn: task1) { 8 doFirst { 9 println ‘I am dependent1’ 10 } 11 } 12 13…… Continue reading Creating dependent tasks
Retrieving query parameters in JAX-RS annotated method
The post explains different ways of retrieving query parameters in JAX-RS annotated method. Below is the complete code 1 package resource; 2 3 import javax.ws.rs.GET; 4 import javax.ws.rs.Path; 5 import javax.ws.rs.QueryParam; 6 import javax.ws.rs.core.Context; 7 import javax.ws.rs.core.MediaType; 8 import javax.ws.rs.core.Response; 9 import javax.ws.rs.core.UriInfo; 10 11 @Path(“webresource2”) 12 public class WebResource2 { 13 @GET 14 @Path(“queryParameters1”)…… Continue reading Retrieving query parameters in JAX-RS annotated method
Simple JsonPatch Example
JsonPatch is a format for storing a sequence of operations that has to be applied on the target json structure. The following operations can be stored in JsonPath and operated on json structure 1) add 2) remove 3) replace 4) move 5) copy 6) test Java jdk provides api for creating JsonPatch. The post explains…… Continue reading Simple JsonPatch Example
Creating and executing task
Gradle is domain specific language where the domain in this case is automating application build process. Gradle consists of Projects and Tasks. Each project has multiple Tasks and each Task has multiple actions. In this post I will explain how to create and execute task. Create a file by name build.gradle with the below code…… Continue reading Creating and executing task
Marshaling a property as xml attribute
By default when marshaling to xml file, all properties are marshaled as elements. This default behaviour can be changed and this post explains how to do it. In this post I will marshall the below java bean class, and id property as its attribute. Country 1 package package1; 2 3 import javax.xml.bind.annotation.XmlAttribute; 4 import javax.xml.bind.annotation.XmlRootElement;…… Continue reading Marshaling a property as xml attribute
Preventing a property from being marshalled to xml file
By default all properties of an instance are marshalled as elements in an xml file. As shown below.. Marshalling an Country insance with below class structure Country package package2; import javax.xml.bind.annotation.XmlRootElement; @XmlRootElement public class Country { private int id; private String name; private int population; public int getId() { return id; } public void setId(int…… Continue reading Preventing a property from being marshalled to xml file
Setting Filter at Logger level
In the post “Setting Filter at Handler level”, I showed how to set filter at handler level. In this post I will explain how to set filter at logger level. An use case of setting filter at logger level, is restricting logging of messages based on the user who logged it. Custom Filter 1 package…… Continue reading Setting Filter at Logger level
Setting Filter at Handler level
Java logging provides log levels at logger and handler level, to filter the messages. To make sure only required messages are logged. We can extend this functionality and provide our own filter, which will filter messages based on message’s metadata in addition to filtering by log levels. We can add this filter at logger level…… Continue reading Setting Filter at Handler level
Supplier Functional Interface Example
Java 8 added a new functional interface named “Supplier”. The purpose of this interface is to supply instances. I will be explaining using the below example. In the example I have want of list of employees. I will separate the logic behind employee instance creation and adding to list. The employee instance will be created…… Continue reading Supplier Functional Interface Example
Code Recipes Blog 