| 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

OpenSuse 42.2 and Synaptics Touch-Pads; Telephone System Quotes for Cat Soft LLC; Even; Cherry Jam; Lebanese Writer Amin Maalouf; Learning From Trump; Chinese Writer Hu Fayun; C++ - it's the language of the future; And; Apricot Jam; Also; Excellent Article on USA Politics; Oh Metafilter; Prejudice Against The Rurals; Also, Zizek; Trump; Why Trump Won; Doxygen + Latex on CentOS 6; SMASH - Solve 5 Biggest Problems in Physics; Good article on racism, brexit, and social divides; Grandaddy are back!; Consciousness From Max Entropy; Democrats; Harvard Will Fix Black Poverty; Modelling Bicycle Wheels; Amusing Polling Outlier; If Labour keeps telling working class people...; Populism and Choice; Books on Defeat; Enrique Ferrari - Argentine Author; Transcript of German Scientists on Learning of Hiroshima; Calvert Journal; Owen Jones on Twitter; Possible Japanese Authors; Complex American Literature; Chutney v5; Weird Componentized Virus; Interesting Argentinian Author - Antonio Di Benedetto; Useful Thread on MetaPhysics; RAND on fighting online anarchy (2001); NSA Hacked; Very Good LRB Article on Brexit; Nussbaum on Anger; Tasting; Apple + Kiwi Jam; Hit Me; Sudoku - CSP + Chaos; Recycling Electronics In Santiago; Vector Displays in OpenGL; And Anti-Aliased; OpenGL - Render via Intermediate Texture; And Garmin Connect; Using Garmin Forerunner 230 With Linux; (Beating Dead Horse) StackOverflow; Current State of Justice in China; Axiom of Determinacy; Ewww; Fee Chaos Book; Course on Differential Geometry; Okay, but...; Sparse Matrices, Deep Learning; Sounds Bad; Applebaum Rape; Tomato Chutney v4; Have to add...; Culturally Liberal and Nothing More; Weird Finite / Infinite Result; Your diamond is a beaten up mess; Maths Books; Good Bike Route from Providencia / Las Condes to Panul; Iain Pears (Author of Complex Plots); Plum Jam; Excellent; More Recently; For a moment I forgot StackOverflow sucked; A Few Weeks On...; Chilean Book Recommendations; How To Write Shared Libraries; Jenny Erpenbeck (Author); Dijkstra, Coins, Tables; Python libraries error on OpenSuse; Deserving Trump; And Smugness; McCloskey Economics Trilogy; cmocka - Mocks for C; Concept Creep (Americans); Futhark - OpenCL Language; Moved / Gone; Fan and USB issues; Burgers in Santiago; The Origin of Icosahedral Symmetry in Viruses; autoenum on PyPI; Jars Explains; Tomato Chutney v3; REST; US Elections and Gender: 24 Point Swing; PPPoE on OpenSuse Leap 42.1; SuperMicro X10SDV-TLN4F/F with Opensuse Leap 42.1; Big Data AI Could Be Very Bad Indeed....; Cornering; Postcapitalism (Paul Mason)

© 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