theotherian

## ClientFactory.java
import javax.ws.rs.client.Client;
import javax.ws.rs.client.ClientBuilder;

import org.apache.http.HttpHost;
import org.apache.http.conn.routing.HttpRoute;
import org.apache.http.impl.conn.PoolingClientConnectionManager;
import org.glassfish.jersey.apache.connector.ApacheClientProperties;
import org.glassfish.jersey.apache.connector.ApacheConnector;
import org.glassfish.jersey.client.ClientConfig;
import org.glassfish.jersey.client.ClientProperties;

## Jersey 2.0 client with generics
It's easy to use Generics with Jersey 2.0 client

## ByteBuffer side effects
Using ByteBuffer instances to allocate memory can be dodgy

## Jersey 2.0 servlet dependencies
There are two dependencies that Jersey 2.0 has for adapting its application to a Servlet instance.

## Start in-memory HSQLDB server
An example of creating an in-memory HSQLDB server

## Hibernate WTF - joins and max results
Don't mix eager or subselect joins with max results; the by product is pretty nasty.

Subselects can select all entities in the associated table, and potentially issue an additional select for each parent, while joins often load duplicate entities due to the max results being applied to the row and not the parent.

## Maven Archetypes Part 3
Files for creating a Maven Archtype - part 3

## Maven Archetypes Part 2
Files for creating Maven archetypes - part 2

## Thread Local DNS 1.0-RC3 dependency definition
XML for pom files to declare a dependency on Thread Local DNS

## Maven Archetypes Part 1
Files for creating Maven Archetypes - part 1
	import javax.ws.rs.client.Client;
	import javax.ws.rs.client.ClientBuilder;

	import org.apache.http.HttpHost;
	import org.apache.http.conn.routing.HttpRoute;
	import org.apache.http.impl.conn.PoolingClientConnectionManager;
	import org.glassfish.jersey.apache.connector.ApacheClientProperties;
	import org.glassfish.jersey.apache.connector.ApacheConnector;
	import org.glassfish.jersey.client.ClientConfig;
	import org.glassfish.jersey.client.ClientProperties;
	Don't mix eager or subselect joins with max results; the by product is pretty nasty.

	Subselects can select all entities in the associated table, and potentially issue an additional select for each parent, while joins often load duplicate entities due to the max results being applied to the row and not the parent.