This has come up recently; the simple idea is that the when injecting a Hibernate Session and additional annotation may be present to identify *which* session to inject. However, this raises another problem ... ValueEncoders and determining which session to use to convert from a string id back to an entity. If the same entity can appear across multiple PUs, this becomes an intractable problem.
On Wed, Dec 2, 2009 at 9:17 AM, Pierce T. Wetter III <pie...@paceap.com> wrote: > > Just this morning, I was looking at a Grid fed by JPAGridDataSource. > > Which means that tapestry-jpa should now be at feature parity with > tapestry-hibernate. (or rather, tapestry-jpa2, and tapestry-jpa2-c are > because we needed features in JPA 2.0) > > http://kenai.com/projects/tapestry-jpa > > It would be nice though if tapestry-jpa could support multiple persistence > units. Since you did the design for the original tapestry-hibernate, I was > wondering if you had any suggestions for how we could tweak the > tapestry-hibernate API to work with multiple PUs. > > Pierce -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
