The DAO exposed by the package should have a minimal API

[eepstein]

Since most consumers of the package are expected to subclass the User and Role entities for their implementations, our DAO should only expose methods needed to support Shiro security.

We can use the current DAO as part of the overall test harness.

[eepstein]

[4/20/13 5:57:27 PM] Ezra Epstein: In terms of making this more general-purpose, the approach I'd take is to keep our User and Role impls within the jdbi package and have them be for internal purposes only.  I'd have the API based on IUser and IRole interfaces.  And even on the impl level I'd have the DefaultJdbiUserDAO take optional class names for the classes to instantiate as User and Role instances.
[4/20/13 5:57:51 PM] Ezra Epstein: Or maybe no need for the last part, since except for the ShiroRealm no one should need to use that DAO.
[4/20/13 5:58:36 PM] Ezra Epstein: and the JdbiDAO makes LOTS of assumptions about how the User and Role are mapped to the database.  So the plug point would be to allow a consumer to provide their own DAO that returns IUser and IRole objects.