On Mon, Jul 19, 2010 at 11:18 PM, Pierce Wetter <pie...@paceap.com> wrote:
> > On Jul 15, 2010, at 11:33 PM, Andreas Andreou wrote: > >> Pierce raises a valid point though - tapestry-hibernate ideally shouldn't >> need >> to depend on internal core / ioc classes > > Exactly! Is that a bug in tapestry or tapestry-hibernate? Well that's definetely not a bug. Andreas talked right, he said "ideally", but tapestry-hibernate is a library around (very near) the core framework so if it choose to depend on an "internal" implementation it's a library's owner choice. What has not to be done is to public (in any way) the internal API on which the module/library depends on. This is the same choice ChenilleKit as done since day one. Cheers -- Massimo http://meridio.blogspot.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
