Plan - Able

A brief page to figure out the plan of stuff to do...

-~~address difference/overlap between /WEB-INF/tags/form~~* and /WEB-INF/tags/able/*--
- resolution - merge them, just need to figure out the [Tag Naming]
-~~make all code that looks at annotations for a method (readMethod.getAnnotation) also look at the field itself. This is The Stripes Way, and we should also do that.~~-
-~~pull out the able-core concept (i'm fine with this)~~-
- -~~what is the contents? Or rather what should stay in able-web?~~-
- -~~generate the JSP thingy?~~-
-~~document everything~~-
- -~~hibernate validation~~-
- -~~customizing views etc~~-
-~~remove references to cparty and check that the view filters are OK etc?~~-
-~~decide on either using the "action" sub package or the "stripes" subpackage~~-
- using action in the demo application, but stripes in the able-core utility library
-~~move "entity" package to something a little less "in the way", like "util.entity". right now people might think that is where models should go~~-
- moved it to the able.introspect module as we might end up with some other introspection code too (e.g. services etc)
-~~move "mail" to "service.mail"~~-
-~~new Resolution type to look for views~~-

able-core - the core jar with useful utility code in there (like the introspection code & JPA helper classes)
able-archetype - the 'empty' project ready to be used by folks
able-demo - a demo web app with a test suite showing a crud-ish example application etc.

-~~any codegen at all for this first release, and if so how: from the able maven plugin, or by letting the generic CRUD tags have a mode that lets them create the JSP for you~~-
maven archetype
- no way to test yet - so we'll do that later