No that's fine. I'm thinking of scrapping the release this week anyways. Too many little things are popping up and I'm getting nervous. We can try again next week and use the extra days to do more testing / tweaking of things.
As for your problem I don't think it has to do with page pooling but with the changes to the ClassFactoryImpl being used. I was having issues adding event registration stuff using the hivemind service-implementation override logic in it and resorted to creating a new tapestry.ClassPool service id instead. Perhaps there is a way to register these reset events another way (or possibly it is another thing that gets auto bound) . You are probably using tapestry-prop on your home page and it can't find the classes as it's using the old hivemind.ClassPool class pool. (possibly) On 6/25/07, Ben Dotte <[EMAIL PROTECTED]> wrote:
Wait a sec.. 48 hours from yesterday still gives me another day. *smacks forehead* Nevermind the time extension. I'll continue taking a look at the page pooling changes. <snipped>
-- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
