Not sure that the DataObjects will work... the live service class reloading basically works b/c there's the public interface, and the "private" implementation, and the only class that has a reference to the private implementation is the proxy. At least, that's how I understand it. ;) Not sure how that would fly with the data objects, unless you defined an interface on top of each of your data objects... which sounds kinda ugly...
Robert On Dec 16, 2010, at 12/169:31 PM , Michael Gentry wrote: > Early Christmas! > > I'm curious to see how the page pooling changes work out. About six > weeks ago one of our production apps blew up on us due to the page > pool. We thought we had large enough sizes defined, but an external > API we depended upon started responding very slowly (after months of > responding quickly) and that led to our pages being checked out of the > pool for minutes at a time, which quickly exhausted the pool. I think > with the removal of the page pool, our app would've survived better > (even though the portion using the external API would've still been > crippled). > > I'm also going to see if I can treat my Cayenne DataObjects as a > "service" for live class reloading now, too. > > Thanks Howard and everyone else who contributed! > > mrg > > > On Thu, Dec 16, 2010 at 5:44 PM, Howard Lewis Ship <hls...@gmail.com> wrote: >> With formatting: >> http://tapestryjava.blogspot.com/2010/12/announcing-tapestry-52.html > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
