Got the design patterns for Java-EnsEMBL reasonably solid in my mind now. This just leaves lots of coding to give nice Java classes for each EnsEMBL data type. I can't help feeling that it ought to be possible to autogenerate a lot of this from the SQL schema. But realistically, there's just enough `exciting' behaviour which has to be woven in that autogeneration probably isn't an option at the moment. Heigh ho (and lets hope the objects don't need to change too much in the future...)