Skip to content

Bind Java objects to URL Encoded Forms similar to JSON-B or JAX-B, and a JAX-RS Form Encoding MessageBodyWriter/Reader

License

Notifications You must be signed in to change notification settings

exabrial/form-binding

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

14 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Form Binding

I looked far and wide and was surprised that there was no annotation based way to bind Form URL Encoded string to a Java Object. Think of this project like JAX-B or JSON-B, but for Form URL Encoding.

License

All files are Licensed Apache Source License 2.0. Please consider contributing back any changes you may make, thanks!

Usage

There are two parts, and API jar and a implementation jar. Include the API jar in your project as a compile dependency, and the implementation jar as a runtime dependency. Annotate your fields (or don't, the default behavior uses the field name and looks at any fields not marked as transient). The Java SPI system will load the implementation for you.

Internally this project makes heavy use of Apache Bean Utils ConvertUtils to convert between strings and value types. You can even extend this behavior by implementing FormBindingConverter and packaging it as a Java SPI Service.

Maven Coordinates

API Jar:

<dependency>
	<groupId>com.github.exabrial</groupId>
	<artifactId>form-binding-api</artifactId>
	<version>SEE THE RELEASES TAB FOR VERSION NUMBER</version>
	<scope>compile</scope>
</dependency>

Runtime Jar:

<dependency>
	<groupId>com.github.exabrial</groupId>
	<artifactId>form-binding</artifactId>
	<version>SEE THE RELEASES TAB FOR VERSION NUMBER</version>
	<scope>runtime</scope>
</dependency>

Binding your classes

  • The default behavior is to bind all of your fields that are not marked @FormBindingTransient
  • If any field is marked as a @FormBindingParam, only fields that are marked with @FormBindingParam will be serialized
  • You can change the name of the parameter bound like this: @FormBindingParam(paramName = "differentName")

Example:

public class MixedAnnotations {
	@FormBindingParam(paramName = "differentName")
	private String heresAField = "Here's a field!!!";
	@FormBindingTransient
	private String ignoreMe = "Don't encode this!!";
	private String heresANonAnnotatedField = "It shouldn't be included";
}

Java Object -> Form URL Encoded String

FormBindingWriter writer = FormBinding.getWriter();
String form = writer.write(new MixedAnnotations());

Will produce:

differentName=Here%27s+a+field%21%21%21

Form URL Encoded String -> Java Object

String input = "differentName=ConvertingBackToJavaObject";
MixedAnnotations mixedAnnotations = reader.read(input, MixedAnnotations.class);

On the returned object, heresAField the field will be set to: ConvertingBackToJavaObject

Implementing your own converter

  • Bean Utils does pretty good job with basic types, but if you have nested objects, you'll want to implement your own converter.
  • Simply implement that FormBindingConverter interface, then put a file in META-INF/services named com.github.exabrial.formbinding.FormBindingConverter
  • Inside this file, put the fully qualified classname of your custom implementation
  • See https://github.com/exabrial/form-binding/tree/master/form-binding-test-module for a complete example