> schema param currently refers to a ddl resource,
> not what people would naturally think is the param to set the schema for the repository
You are right, 'schema' is unfortunate. I also thought it means the database schema, and spent a lot of time because of this (actually, twice - the last time two weeks ago). I would love to change it to schemaDDL, the only problem I see is compatibility. What about: support a new setting 'schemaDDL' (or what about just 'ddl', or 'ddlResource'), and change all samples to use this property name. But still support 'schema' as well for backward compatibility.
> - add an optional schema param which allows the user to select which schema they want to use
what about 'schemaName' to avoid a clash with the deprecated 'schema' property? Currently the user name is hard coded (ResultSet rs = metaData.getTables(null, userName, tableName, null))
> - improve error messages so that when an incorrect schemaDDL is chosen the user doesn't have to dig through nabble etc to find an answer
Sure. What about "Configuration error: The resource xyz.ddl could not be found"?