> That's not too hard; the tricky part is the replication of several
> services with the same interface; i.e., you will need an @Product
> HibernateConfigurer and a @Content HibernateConfigurer, etc.
>
> This could all be done, and done on top of tapestry-hibernate without
> changing the framework, I think. The only tricky part is that the
> default HibernateConfigurer assumes that you start by reading
> hibernate.cfg.xml and that would need to be more flexible
> (hibernate-products.cfg.xml, hibernate-session.cfg.xml).
I've thought about implementing this functionality in tapestry-jpa as well.
With JPA we don't have the problem of the configuration as everything
is configured inside persistence.xml. Auto discovery is already
handled by most implementations. No need to do all the configuration
magic present in the hibernate module.
If you want to introduce some way to handle multiple databases in the
hibernate module, maybe it would be a good timeframe to create a
tapestry-persistence module which can be used by other modules like
tapestry-jpa or tapestry-mongodb as well. I am thinking mainly about
annotations like @CommitAfter. But the interface to handle multiple
data sources should be reusable as well.
On a side note, maybe its time for tapestry to get first class JPA2 support?
Piero
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
