Ah, Rob, I'm sure your helpful nature has provided all the technical assistance Henrik needed. I'm still waiting for an answer from you on my inquiries BTW.
Henrik provided enough information from someone who hit that exact problem to understand. There was not enough information for someone to easily reproduce his problems. Henrik, I have used 4.0.x and 5.0.x, so I'm don't have specific experience with 4.1.x. Given that there is a "history" behind the "Visit", I avoid using that name for any application state object. I doubt that is your problem, but you never know. I have never had problems with inherited annotations. Can you provide more of your source? Have you made sure you don't have any old Tapestry jars around? Jonathan > -----Original Message----- > From: Rob Smeets [mailto:[EMAIL PROTECTED] > Sent: Wednesday, May 07, 2008 9:08 AM > To: Tapestry users > Subject: Re: [T4.1.5] - Inherited annotations fail > > No one responding? Sounds like a deja vu. That's sad! > Normally, it's Jesse Kuhnert who is responsible for T4 related issues. But > unfortunately he's left Tapestry. You may do so too. I wish you best of > luck. > > Yours friendly, > > Rob > > On Tue, May 6, 2008 at 5:53 AM, Henrik Schlanbusch <[EMAIL PROTECTED]> > wrote: > > > Hi again... still no luck with this one. > > > > After an intense night debugging this, I have found > > that the bug appears consequently the *second* > > browser instance that hits the same page. The first > > request to the page runs fine, but the second time > > (with a new browser instance) will produce the exception. > > > > I am really stuck here - is tapestry caching some > > of my components here or is it something else > > going on. I have logged out from ComponentSpecification > > and it actually finds that my component has already > > been added to the page specification. > > > > I really hope someone can shed some light on this > > because this is a serious blocker to our > > project. > > > > Best, > > Henrik > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
