t that this looks like a bug, but
I'll
investigate you're workaround and see if we can make that work as
a
stop-gap.
-Original Message-
From: Shawn Church [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 04, 2005 10:12 AM
To: tapestry-user@ja
e of the requests will receive this same stack
> trace.
> > >
> > > I agree with your assessment that this looks like a bug, but
> I'll
> > > investigate you're workaround and see if we can make that work as
> a
> > > stop-gap.
&
with your assessment that this looks like a bug, but I'll
> > investigate you're workaround and see if we can make that work as a
> > stop-gap.
> >
> > -Original Message-
> > From: Shawn Church [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, Octo
age-
> From: Shawn Church [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, October 04, 2005 10:12 AM
> To: tapestry-user@jakarta.apache.org
> Subject: Re: InjectState exception within activateExternalPage
>
> The only solution (work-around) I could come up with for this problem
t work as a
stop-gap.
-Original Message-
From: Shawn Church [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 04, 2005 10:12 AM
To: tapestry-user@jakarta.apache.org
Subject: Re: InjectState exception within activateExternalPage
The only solution (work-around) I could come up with for this p
The only solution (work-around) I could come up with for this problem is
to replace this in my Border component:
@InjectState("visit")
public abstract Visit getVisitObject();
with this:
@InjectObject("infrastructure:applicationStateManager")
public abstract ApplicationStateManage
