I agree, we have no problem removing prop: with the ognl speed enhancements. We only left prop: there because there wasn't a good reason to remove it (until now). If anything it might be nice to have a note about it by the new release.
-----Original Message----- From: Marcus Schulte [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 26, 2007 1:35 AM To: Tapestry development Subject: Re: [vote] Release Tapestry 4.1.2 Good to hear! I think the prop-problem is not too bad since the new ognl should make speed differences negligible anyway. 2007/6/26, Jesse Kuhnert <[EMAIL PROTECTED]>: > > I may continue with the release after all... The ClassFactory problem is > not > fixable because of cyclic dependencies between it and BuilderFactory (or > something builder factory uses). I can't bare the thought of watching my > vm > slowly consume all memory in dev mode so I may just have to thumb my nose > at > the tapestry-prop users..... I'm not sure about this one. If anyone has > any suggestions that wouldn't result in angry tapestry-prop users I'd be > all > for hearing it. (though I think it may still be easier to just tell them > to stop using it, or it can have a new special 4.1.2 tapestry compatible > release that uses the new tapestry.ClassPool service point instead of > hivemind.ClassPool ) > > The other concerning issue with character encoding wasn't Tapestry's fault > (ognl) so I'm not as scared anymore.. > > On 6/25/07, Ben Dotte <[EMAIL PROTECTED]> wrote: > > > > You're right, I replaced all uses of prop: with ognl:, fixed up a couple > > other things, and the home page comes up again. Other parts of the app > > look ok too from a cursory glance. > > > > If you don't scrap the release I am +1 (binding). > > > > Otherwise I will be sure to test it again next week. > > > > Thanks, > > Ben > > > > -----Original Message----- > > From: Jesse Kuhnert [mailto:[EMAIL PROTECTED] > > Sent: Monday, June 25, 2007 11:15 AM > > To: Tapestry development > > Subject: Re: [vote] Release Tapestry 4.1.2 > > > > 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 > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Jesse Kuhnert > Tapestry/Dojo team member/developer > > Open source based consulting work centered around > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com > -- Marcus Schulte http://marcus-schulte.blogspot.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
