Architecture of the Honeycomb Tapestry-Hibernate Integration Layer
Note: This is work in progress. Anyway, comments are welcome.
Generally, Honeycomb aims to implement a Tapestry Hibernate integration adhering to the principles described here.
Where Honeycomb plugs into Tapestry
Honeycomb supplements Tapestry with
- A custom "conversation"-scope for persistent page properties with a lifecycle between that of a request and session. An ASO (application state object) with this scope is used as the backing store for the Hibernate-Sessions' service-state. It may be interesting to note that the conversation scope is a remarkable (if somewhat "overdesigned") example for HiveMind's support to support cyclic dependencies: It's implemented as a session-scoped ASO which, in turn, holds all conversation scoped persistent properties - and ASO's.
- A SqueezeAdaptor, to translate Hibernate entities into their entity-name plus their id (back and forth).
- An override for the DirectService putting it in transactional brackets.
Dynamics of a request
