The reason for my lack of sleep and blogging in the last 6 weeks is ready for an initial release: http://bowlerframework.org/
A lot of the ideas in the framework have been discussed on this blog previously, for instance: I’ve tried to keep the “Resource View” (resource being rendered in REST lingo) as separate as possible from concerns such as layout.
To kind of give a quick indication of the framework, I would best explain it as having tried to get the approachability and productivity of Rails and Play Framework, with UI re-use and composability somewhere in between Apache Wicket Components/Panels and Lift Snippets, while adding in my own little flavour and ideas.
Also, testability is something I’ve taken seriously, so any Bowler app that is written well should be very easily testable entirely without a container.
This is a “0.1” release, so it will more than likely contain bugs and gaps in thinking. Though I’m hoping community feedback and contributions will fix that soon enough!