| Andrew Cooke | Contents | Latest | RSS | Twitter | Previous | Next

C[omp]ute

Welcome to my blog, which was once a mailing list of the same name and is still generated by mail. Please reply via the "comment" links.

Always interested in offers/projects/new ideas. Eclectic experience in fields like: numerical computing; Python web; Java enterprise; functional languages; GPGPU; SQL databases; etc. Based in Santiago, Chile; telecommute worldwide. CV; email.

Personal Projects

Lepl parser for Python.

Colorless Green.

Photography around Santiago.

SVG experiment.

Professional Portfolio

Calibration of seismometers.

Data access via web services.

Cache rewrite.

Extending OpenSSH.

C-ORM: docs, API.

Last 100 entries

The Davalos Affair For Idiots; Not The Onion: Google Fireside Chat w Kissinger; Bicycle Wheels, Inertia, and Energy; Another Tax Fraud; Google's Borg; A Verion That Redirects To Local HTTP Server; Spanish Accents For Idiots; Aluminium Cans; Advice on Spray Painting; Female View of Online Chat From a Male; UX Reading List; S4 Subgroups - Geometric Interpretation; Fucking Email; The SQM Affair For Idiots; Using Kolmogorov Complexity; Oblique Strategies in bash; Curses Tools; Markov Chain Monte Carlo Without all the Bullshit; Email Para Matias Godoy Mercado; The Penta Affair For Idiots; Example Code To Create numpy Array in C; Good Article on Bias in Graphic Design (NYTimes); Do You Backup github?; Data Mining Books; SimpleDateFormat should be synchronized; British Words; Chinese Govt Intercepts External Web To DDOS github; Numbering Permutations; Teenage Engineering - Low Price Synths; GCHQ Can Do Whatever It Wants; Dublinesque; A Cryptographic SAT Solver; Security Challenges; Word Lists for Crosswords; 3D Printing and Speaker Design; Searchable Snowden Archive; XCode Backdoored; Derived Apps Have Malware (CIA); Rowhammer - Hacking Software Via Hardware (DRAM) Bugs; Immutable SQL Database (Kinda); Tor GPS Tracker; That PyCon Dongle Mess...; ASCII Fluid Dynamics; Brandalism; Table of Shifter, Cassette and Derailleur Compatability; Lenovo Demonstrates How Bad HTTPS Is; Telegraph Owned by HSBC; Smaptop - Sunrise (Music); Equation Group (NSA); UK Torture in NI; And - A Natural Extension To Regexps; This Is The Future Of Religion; The Shazam (Music Matching) Algorithm; Tributes To Lesbian Community From AIDS Survivors; Nice Rust Summary; List of Good Fiction Books; Constructing JSON From Postgres (Part 2); Constructing JSON From Postgres (Part 1); Postgres in Docker; Why Poor Places Are More Diverse; Smart Writing on Graceland; Satire in France; Free Speech in France; MTB Cornering - Where Should We Point Our Thrusters?; Secure Secure Shell; Java Generics over Primitives; 2014 (Charlie Brooker); How I am 7; Neural Nets Applied to Go; Programming, Business, Social Contracts; Distributed Systems for Fun and Profit; XML and Scheme; Internet Radio Stations (Curated List); Solid Data About Placebos; Half of Americans Think Climate Change Is a Sign of the Apocalypse; Saturday Surf Sessions With Juvenile Delinquents; Ssh, tty, stdout and stderr; Feathers falling in a vacuum; Santiago 30m Bike Route; Mapa de Ciclovias en Santiago; How Unreliable is UDP?; SE Santiago 20m Bike Route; Cameron's Rap; Configuring libxml with Eclipse; Reducing Combinatorial Complexity With Occam - AI; Sentidos Comunes (Chilean Online Magazine); Hilary Mantel: The Assassination of Margaret Thatcher - August 6th 1983; NSA Interceptng Gmail During Delivery; General IIR Filters; What's happening with Scala?; Interesting (But Largely Illegible) Typeface; Retiring Essentialism; Poorest in UK, Poorest in N Europe; I Want To Be A Redneck!; Reverse Racism; The Lost Art Of Nomography; IBM Data Center (Photo); Interesting Account Of Gamma Hack; The Most Interesting Audiophile In The World; How did the first world war actually end?; Ky - Restaurant Santiago; The Black Dork Lives!

© 2006-2015 Andrew Cooke (site) / post authors (content).

Java Annotations to Construct POJOs from HTTP Requests

From: "andrew cooke" <andrew@...>

Date: Wed, 20 Aug 2008 16:25:55 -0400 (CLT)

At work I'm writing code to provide a REST interface to a database (really
it's simpler than that - it's read only).  In the controller I want to
automate the construction of the model as much as possible.  This is
driven by the parameters in the request, so as a first step I want to be
able to set object attributes from the HTTP request.

I also want to be able to generate URLs from these same objects, when they
are modified (so that it is easy to generate URLs in the view to related
information).

So I need to (1) associate attributes with HTTP requests and (2) store
default parameters (so that the generated URI is no longer than
necessary).  After wondering exactly how to go about this I remembered the
rather excellent approach taken by args4j - https://args4j.dev.java.net/ -
which uses annotations on attributions.

It turns out that this is incredibly easy to do.  I now have some simple
annotations that let me define a tree of objects that will be
automatically generated with attributes populated from the request (which
tree is generated will depend on some other logic using the URI).

Here's the test (this is work's code, so it's (c) ISTI http://www.isti.com
and available under an attribution-based licence; contact ISTI for full
details).

public class BuilderTest
{

  @Test
  public void testAll()
  throws IllegalArgumentException, SecurityException, InstantiationException,
  IllegalAccessException, InvocationTargetException, NoSuchMethodException {
    MockHttpServletRequest request = new MockHttpServletRequest();
    request.setParameter("value-1", "one");
    request.setParameter("value-3", "3");
    request.setParameter("value-a", "a");
    request.setParameter("value-b", "5");
    Builder builder = new Builder(request);
    Outer outer = builder.build(Outer.class);
    assertEquals("Bad value for value1", "one", outer.value1);
    assertEquals("Bad value for value2", "default", outer.value2);
    assertEquals("Bad value for value3", 3, outer.value3);
    assertEquals("Bad value for valuea", "a", outer.inner.valuea);
    assertEquals("Bad value for valueb", 5, outer.inner.valueb, 0.001);
  }

  public static class Outer {
    @Parameter(deflt = "", name = "value-1")
    public String value1;
    @Parameter(deflt = "default", name = "value-2")
    public String value2;
    @Parameter(deflt = "", name = "value-3")
    public int value3;
    @Parameterised
    public Inner inner;
  }

  public static class BaseInner {
    @Parameter(deflt = "", name = "value-a")
    public String valuea;
  }

  public static class Inner extends BaseInner {
    @Parameter(deflt = "", name = "value-b")
    public double valueb;
  }

}

And you can see that:
1 - attributes are set from the HTTP request
2 - defaults are supplied as necessary
3 - a tree of objects can be created

The implementation is simple (the annotations themselves are trivial
interfaces).  All the work is done in the Builder, mainly in these
methods:

public <Type> Type build(final Class<Type> clazz)
{
  Type instance = clazz.getConstructor().newInstance();
  // if we use getDeclaredFields here we don't superclass fields.
  // unfortunately, this then restricts us to public fields (declared
  // seems to also include protected fields)
  for (Field field: clazz.getFields()) {
    setParameter(instance, field);
    extendParameterised(instance, field);
  }
  return instance;
}

private <Type> void setParameter(final Type instance, final Field field)
{
  logger.debug("Field {}", field.getName());
  Parameter parameter = field.getAnnotation(Parameter.class);
  if (parameter != null) {
    String value = getValue(parameter);
    if (field.getType() == String.class) {
      field.set(instance, value);
    } else if (field.getType() == Integer.TYPE) {
      field.setInt(instance, Integer.parseInt(value));
    } else if (field.getType() == Double.TYPE) {
      field.setDouble(instance, Double.parseDouble(value));
    } else {
      throw new BadParameterException(
        String.format("Bad type %s for %s = %s.",
                      field.getType().getSimpleName(),
                      parameter.name(), value));
    }
  }
}

private <Type> void extendParameterised(
    final Type instance, final Field field)
{
  if (field.isAnnotationPresent(Parameterised.class)) {
    field.set(instance, build(field.getType()));
  }
}

Andrew

Spring's Command Controller

From: "andrew cooke" <andrew@...>

Date: Wed, 20 Aug 2008 17:11:55 -0400 (CLT)

...is kind-of similar.  The differences (from the point of view of the
Spring class are):

- Proper Java bean support (setters rather than attributes)
- Wider range of values via Java bean property editors
- Dotted paths (rather than single flat namespace)
- No defaults (which makes constructing compact URIs hard)
- No annotations (as far as I can see) to restrict what is set
  (instead uses standard "public" interface)
- Validators (not needed in my read-only case, thankfully)

Validators and property conversion are the biggies, but in my case
constructing URIs and a flat namespace are what I need.

Andrew

Comment on this post