Re: The active page name has not been specified
Yes, still having the same issue, but only on the my Ajax form. My form is
very complicating, so I'll try breaking it down into something simpler
tomorrow and hopefully pin point the issue. My submit buttons are up top
and I think I'm using defer true, so I'm not sure if that has something to
do with it. I also have some logic in my onActivate method, but I figured
the redirection should have been happening before that method was ever
called.
On Mar 31, 2015 4:35 PM, "Dimitris Zenios"
wrote:
> Did you try the exclusion i told you about?
>
> On Tue, Mar 31, 2015 at 11:32 PM, George Christman <
> gchrist...@cardaddy.com>
> wrote:
>
> > Thanks Dimitris, I'm guessing there is a bug in my code. I went to
> another
> > page in my app where I have an ajaxformloop and it appeared to redirect
> > without issue. I'm going to have to dig deeper tomorrow to find the cause
> > of this issue.
> >
> > On Tue, Mar 31, 2015 at 4:25 PM, Dimitris Zenios <
> > dimitris.zen...@gmail.com>
> > wrote:
> >
> > > When you include a tynamo dependency do you exclude the tapestry-core
> and
> > > tapestry-ioc like I did? If you don't then you end up having
> > tapestry-core
> > > 5.4-beta22 and tapestry-core 5.4-beta28 in your class path which might
> be
> > > the source of your problem
> > >
> > > On Tue, Mar 31, 2015 at 11:24 PM, Dimitris Zenios <
> > > dimitris.zen...@gmail.com
> > > > wrote:
> > >
> > > >
> > > > > > t:title="message:add-department-label">
> > > >
> > > > > > t:validate="department">
> > > >
> > > >
> > > > > > t:mixins="formGroup"/>
> > > > t:value="department.parent"
> > > t:model="departmentsModelEncoder"
> > > > t:encoder="departmentsModelEncoder"
> > > t:mixins="formGroup"/>
> > > > > > t:value="department.manager" t:model="viewDepartment.usersModelEncoder"
> > > >
> > > t:encoder="viewDepartment.usersModelEncoder" t:mixins="formGroup"
> > > t:blankoption="ALWAYS"/>
> > > > > > t:value="department.defaultSchedule"
> > > >
> > > t:model="viewDepartment.schedulesModelEncoder"
> > > t:encoder="viewDepartment.schedulesModelEncoder"
> > > > t:mixins="formGroup"
> > > t:blankoption="ALWAYS" t:validate="required"/>
> > > > t:value="department.notes"
> > > t:mixins="formGroup" rows="5"/>
> > > >
> > > >
> > > > ${message:submit-label}
> > > > > > data-dismiss="modal">${message:close-label}
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > On Tue, Mar 31, 2015 at 11:19 PM, George Christman <
> > > > gchrist...@cardaddy.com> wrote:
> > > >
> > > >> And your wrapping your form in a zone too? Sorry, I just want to be
> > sure
> > > >> we
> > > >> are doing everything the same.
> > > >>
> > > >> On Tue, Mar 31, 2015 at 4:05 PM, Dimitris Zenios <
> > > >> dimitris.zen...@gmail.com>
> > > >> wrote:
> > > >>
> > > >> > Fedora 3.19.1-201.fc21.x86_64 #1 SMP Wed Mar 18 04:29:24 UTC 2015
> > > x86_64
> > > >> > x86_64 x86_64 GNU/Linux
> > > >> > Java 1.8.0_40
> > > >> > Google chrome Version 41.0.2272.101 (64-bit)
> > > >> > jetty-distribution-9.2.5.v20141112
> > > >> > Tapestry 5.4-beta28
> > > >> >
> > > >> > org.tynamo
> > > >> > tapestry-security
> > > >> > 0.6.2
> > > >> >
> > > >> >
> > > >> > org.apache.tapestry
> > > >> > tapestry-core
> > > >> >
> > > >> >
> > > >> > org.apache.tapestry
> > > >> > tapestry-ioc
> > > >> >
> > > >> >
> > > >> >
> > > >> >
> > > >> > I am doing the same test as you do (Moving the clock forward). I
> > also
> > > >> tried
> > > >> > 1.Removing the cookie
> > > >> > 2.Normal session time out by setting the time out to 1 minute
> > > (Web.xml)
> > > >> > 3.Doing session invalidate.
> > > >> >
> > > >> > All of those tests had the same result.Once the form is submitted
> > the
> > > >> user
> > > >> > is redirected back to login page.
> > > >> >
> > > >> > On Tue, Mar 31, 2015 at 9:35 PM, Chris Poulsen <
> > > mailingl...@nesluop.dk>
> > > >> > wrote:
> > > >> >
> > > >> > > I think I've seen the error during debugging here and there in
> > > >> beta-22...
> > > >> > > We're not using tapestry security, I can't remember if it
> happens
> > > when
> > > >> > I'm
> > > >> > > too slow in the javascript debugger or it is during serverside
> > > >> debugging
> > > >> > -
> > > >> > > I'll keep an eye out for it.
> > > >> > >
> > > >> > > We have a conversation moderator in play on some pages - similar
> > to
> > > >> the
> > > >> > one
> > > >> > > in tynamo conversations, so requests may arrive while things are
> > > >> locked
> > > >> > up
> > > >> > > in either debugger - but I cannot remember if this has happened
> on
> > > >
Re: The active page name has not been specified
Thanks Dimitris, I'm guessing there is a bug in my code. I went to another
page in my app where I have an ajaxformloop and it appeared to redirect
without issue. I'm going to have to dig deeper tomorrow to find the cause
of this issue.
On Tue, Mar 31, 2015 at 4:25 PM, Dimitris Zenios
wrote:
> When you include a tynamo dependency do you exclude the tapestry-core and
> tapestry-ioc like I did? If you don't then you end up having tapestry-core
> 5.4-beta22 and tapestry-core 5.4-beta28 in your class path which might be
> the source of your problem
>
> On Tue, Mar 31, 2015 at 11:24 PM, Dimitris Zenios <
> dimitris.zen...@gmail.com
> > wrote:
>
> >
> > t:title="message:add-department-label">
> >
> > t:validate="department">
> >
> >
> > t:mixins="formGroup"/>
> > t:model="departmentsModelEncoder"
> > t:encoder="departmentsModelEncoder"
> t:mixins="formGroup"/>
> > t:value="department.manager" t:model="viewDepartment.usersModelEncoder"
> >
> t:encoder="viewDepartment.usersModelEncoder" t:mixins="formGroup"
> t:blankoption="ALWAYS"/>
> > t:value="department.defaultSchedule"
> >
> t:model="viewDepartment.schedulesModelEncoder"
> t:encoder="viewDepartment.schedulesModelEncoder"
> > t:mixins="formGroup"
> t:blankoption="ALWAYS" t:validate="required"/>
> > t:mixins="formGroup" rows="5"/>
> >
> >
> > ${message:submit-label}
> > data-dismiss="modal">${message:close-label}
> >
> >
> >
> >
> >
> >
> >
> > On Tue, Mar 31, 2015 at 11:19 PM, George Christman <
> > gchrist...@cardaddy.com> wrote:
> >
> >> And your wrapping your form in a zone too? Sorry, I just want to be sure
> >> we
> >> are doing everything the same.
> >>
> >> On Tue, Mar 31, 2015 at 4:05 PM, Dimitris Zenios <
> >> dimitris.zen...@gmail.com>
> >> wrote:
> >>
> >> > Fedora 3.19.1-201.fc21.x86_64 #1 SMP Wed Mar 18 04:29:24 UTC 2015
> x86_64
> >> > x86_64 x86_64 GNU/Linux
> >> > Java 1.8.0_40
> >> > Google chrome Version 41.0.2272.101 (64-bit)
> >> > jetty-distribution-9.2.5.v20141112
> >> > Tapestry 5.4-beta28
> >> >
> >> > org.tynamo
> >> > tapestry-security
> >> > 0.6.2
> >> >
> >> >
> >> > org.apache.tapestry
> >> > tapestry-core
> >> >
> >> >
> >> > org.apache.tapestry
> >> > tapestry-ioc
> >> >
> >> >
> >> >
> >> >
> >> > I am doing the same test as you do (Moving the clock forward). I also
> >> tried
> >> > 1.Removing the cookie
> >> > 2.Normal session time out by setting the time out to 1 minute
> (Web.xml)
> >> > 3.Doing session invalidate.
> >> >
> >> > All of those tests had the same result.Once the form is submitted the
> >> user
> >> > is redirected back to login page.
> >> >
> >> > On Tue, Mar 31, 2015 at 9:35 PM, Chris Poulsen <
> mailingl...@nesluop.dk>
> >> > wrote:
> >> >
> >> > > I think I've seen the error during debugging here and there in
> >> beta-22...
> >> > > We're not using tapestry security, I can't remember if it happens
> when
> >> > I'm
> >> > > too slow in the javascript debugger or it is during serverside
> >> debugging
> >> > -
> >> > > I'll keep an eye out for it.
> >> > >
> >> > > We have a conversation moderator in play on some pages - similar to
> >> the
> >> > one
> >> > > in tynamo conversations, so requests may arrive while things are
> >> locked
> >> > up
> >> > > in either debugger - but I cannot remember if this has happened on
> >> pages
> >> > > supporting conversations.
> >> > >
> >> > > --
> >> > > Chris
> >> > >
> >> > > On Tue, Mar 31, 2015 at 7:52 PM, George Christman <
> >> > gchrist...@cardaddy.com
> >> > > >
> >> > > wrote:
> >> > >
> >> > > > Dimitris, I just tested in 5.4-beta-28 with the same exception.
> What
> >> > > > version of tapestry-security are you using? I'm using 0.6.2? Are
> you
> >> > > > submitting with an ajax form? I can reproduce this very easily by
> >> > forcing
> >> > > > my session to expire locally by advancing my computers time and
> then
> >> > > > submitting an ajax form. It happens every single time.
> >> > > >
> >> > > > On Tue, Mar 31, 2015 at 1:36 PM, George Christman <
> >> > > gchrist...@cardaddy.com
> >> > > > >
> >> > > > wrote:
> >> > > >
> >> > > > > I'll test it in beta-28, but until that validation bug gets
> >> fixed, I
> >> > > > can't
> >> > > > > upgrade to it.
> >> > > > >
> >> > > > > On Tue, Mar 31, 2015 at 12:46 PM, Dimitris Zenios <
> >> > > > > dimitris.zen...@gmail.com> wrote:
> >> > > > >
> >> > > > >> FYI just tested with 5.4-beta28 and I don't have such problem
> >> > > > >>
> >> > > > >> On Tue, Mar 31, 2015 at 5:38 PM, George Christman <
> >> > > > >> gchrist...@cardaddy.com>
> >> > > > >> wrote:
Re: The active page name has not been specified
Did you try the exclusion i told you about?
On Tue, Mar 31, 2015 at 11:32 PM, George Christman
wrote:
> Thanks Dimitris, I'm guessing there is a bug in my code. I went to another
> page in my app where I have an ajaxformloop and it appeared to redirect
> without issue. I'm going to have to dig deeper tomorrow to find the cause
> of this issue.
>
> On Tue, Mar 31, 2015 at 4:25 PM, Dimitris Zenios <
> dimitris.zen...@gmail.com>
> wrote:
>
> > When you include a tynamo dependency do you exclude the tapestry-core and
> > tapestry-ioc like I did? If you don't then you end up having
> tapestry-core
> > 5.4-beta22 and tapestry-core 5.4-beta28 in your class path which might be
> > the source of your problem
> >
> > On Tue, Mar 31, 2015 at 11:24 PM, Dimitris Zenios <
> > dimitris.zen...@gmail.com
> > > wrote:
> >
> > >
> > > > t:title="message:add-department-label">
> > >
> > > > t:validate="department">
> > >
> > >
> > > > t:mixins="formGroup"/>
> > > > t:model="departmentsModelEncoder"
> > > t:encoder="departmentsModelEncoder"
> > t:mixins="formGroup"/>
> > > > t:value="department.manager" t:model="viewDepartment.usersModelEncoder"
> > >
> > t:encoder="viewDepartment.usersModelEncoder" t:mixins="formGroup"
> > t:blankoption="ALWAYS"/>
> > > > t:value="department.defaultSchedule"
> > >
> > t:model="viewDepartment.schedulesModelEncoder"
> > t:encoder="viewDepartment.schedulesModelEncoder"
> > > t:mixins="formGroup"
> > t:blankoption="ALWAYS" t:validate="required"/>
> > > > t:mixins="formGroup" rows="5"/>
> > >
> > >
> > > ${message:submit-label}
> > > > data-dismiss="modal">${message:close-label}
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > On Tue, Mar 31, 2015 at 11:19 PM, George Christman <
> > > gchrist...@cardaddy.com> wrote:
> > >
> > >> And your wrapping your form in a zone too? Sorry, I just want to be
> sure
> > >> we
> > >> are doing everything the same.
> > >>
> > >> On Tue, Mar 31, 2015 at 4:05 PM, Dimitris Zenios <
> > >> dimitris.zen...@gmail.com>
> > >> wrote:
> > >>
> > >> > Fedora 3.19.1-201.fc21.x86_64 #1 SMP Wed Mar 18 04:29:24 UTC 2015
> > x86_64
> > >> > x86_64 x86_64 GNU/Linux
> > >> > Java 1.8.0_40
> > >> > Google chrome Version 41.0.2272.101 (64-bit)
> > >> > jetty-distribution-9.2.5.v20141112
> > >> > Tapestry 5.4-beta28
> > >> >
> > >> > org.tynamo
> > >> > tapestry-security
> > >> > 0.6.2
> > >> >
> > >> >
> > >> > org.apache.tapestry
> > >> > tapestry-core
> > >> >
> > >> >
> > >> > org.apache.tapestry
> > >> > tapestry-ioc
> > >> >
> > >> >
> > >> >
> > >> >
> > >> > I am doing the same test as you do (Moving the clock forward). I
> also
> > >> tried
> > >> > 1.Removing the cookie
> > >> > 2.Normal session time out by setting the time out to 1 minute
> > (Web.xml)
> > >> > 3.Doing session invalidate.
> > >> >
> > >> > All of those tests had the same result.Once the form is submitted
> the
> > >> user
> > >> > is redirected back to login page.
> > >> >
> > >> > On Tue, Mar 31, 2015 at 9:35 PM, Chris Poulsen <
> > mailingl...@nesluop.dk>
> > >> > wrote:
> > >> >
> > >> > > I think I've seen the error during debugging here and there in
> > >> beta-22...
> > >> > > We're not using tapestry security, I can't remember if it happens
> > when
> > >> > I'm
> > >> > > too slow in the javascript debugger or it is during serverside
> > >> debugging
> > >> > -
> > >> > > I'll keep an eye out for it.
> > >> > >
> > >> > > We have a conversation moderator in play on some pages - similar
> to
> > >> the
> > >> > one
> > >> > > in tynamo conversations, so requests may arrive while things are
> > >> locked
> > >> > up
> > >> > > in either debugger - but I cannot remember if this has happened on
> > >> pages
> > >> > > supporting conversations.
> > >> > >
> > >> > > --
> > >> > > Chris
> > >> > >
> > >> > > On Tue, Mar 31, 2015 at 7:52 PM, George Christman <
> > >> > gchrist...@cardaddy.com
> > >> > > >
> > >> > > wrote:
> > >> > >
> > >> > > > Dimitris, I just tested in 5.4-beta-28 with the same exception.
> > What
> > >> > > > version of tapestry-security are you using? I'm using 0.6.2? Are
> > you
> > >> > > > submitting with an ajax form? I can reproduce this very easily
> by
> > >> > forcing
> > >> > > > my session to expire locally by advancing my computers time and
> > then
> > >> > > > submitting an ajax form. It happens every single time.
> > >> > > >
> > >> > > > On Tue, Mar 31, 2015 at 1:36 PM, George Christman <
> > >> > > gchrist...@cardaddy.com
> > >> > > > >
> > >> > > > wrote:
> > >> > > >
> > >> > > > > I'll test it in beta-28, but
Re: The active page name has not been specified
When you include a tynamo dependency do you exclude the tapestry-core and
tapestry-ioc like I did? If you don't then you end up having tapestry-core
5.4-beta22 and tapestry-core 5.4-beta28 in your class path which might be
the source of your problem
On Tue, Mar 31, 2015 at 11:24 PM, Dimitris Zenios wrote:
>
> t:title="message:add-department-label">
>
>
>
>
> t:mixins="formGroup"/>
> t:model="departmentsModelEncoder"
> t:encoder="departmentsModelEncoder"
> t:mixins="formGroup"/>
> t:model="viewDepartment.usersModelEncoder"
> t:encoder="viewDepartment.usersModelEncoder"
> t:mixins="formGroup" t:blankoption="ALWAYS"/>
> t:value="department.defaultSchedule"
> t:model="viewDepartment.schedulesModelEncoder"
> t:encoder="viewDepartment.schedulesModelEncoder"
> t:mixins="formGroup" t:blankoption="ALWAYS"
> t:validate="required"/>
> t:mixins="formGroup" rows="5"/>
>
>
> ${message:submit-label}
> data-dismiss="modal">${message:close-label}
>
>
>
>
>
>
>
> On Tue, Mar 31, 2015 at 11:19 PM, George Christman <
> gchrist...@cardaddy.com> wrote:
>
>> And your wrapping your form in a zone too? Sorry, I just want to be sure
>> we
>> are doing everything the same.
>>
>> On Tue, Mar 31, 2015 at 4:05 PM, Dimitris Zenios <
>> dimitris.zen...@gmail.com>
>> wrote:
>>
>> > Fedora 3.19.1-201.fc21.x86_64 #1 SMP Wed Mar 18 04:29:24 UTC 2015 x86_64
>> > x86_64 x86_64 GNU/Linux
>> > Java 1.8.0_40
>> > Google chrome Version 41.0.2272.101 (64-bit)
>> > jetty-distribution-9.2.5.v20141112
>> > Tapestry 5.4-beta28
>> >
>> > org.tynamo
>> > tapestry-security
>> > 0.6.2
>> >
>> >
>> > org.apache.tapestry
>> > tapestry-core
>> >
>> >
>> > org.apache.tapestry
>> > tapestry-ioc
>> >
>> >
>> >
>> >
>> > I am doing the same test as you do (Moving the clock forward). I also
>> tried
>> > 1.Removing the cookie
>> > 2.Normal session time out by setting the time out to 1 minute (Web.xml)
>> > 3.Doing session invalidate.
>> >
>> > All of those tests had the same result.Once the form is submitted the
>> user
>> > is redirected back to login page.
>> >
>> > On Tue, Mar 31, 2015 at 9:35 PM, Chris Poulsen
>> > wrote:
>> >
>> > > I think I've seen the error during debugging here and there in
>> beta-22...
>> > > We're not using tapestry security, I can't remember if it happens when
>> > I'm
>> > > too slow in the javascript debugger or it is during serverside
>> debugging
>> > -
>> > > I'll keep an eye out for it.
>> > >
>> > > We have a conversation moderator in play on some pages - similar to
>> the
>> > one
>> > > in tynamo conversations, so requests may arrive while things are
>> locked
>> > up
>> > > in either debugger - but I cannot remember if this has happened on
>> pages
>> > > supporting conversations.
>> > >
>> > > --
>> > > Chris
>> > >
>> > > On Tue, Mar 31, 2015 at 7:52 PM, George Christman <
>> > gchrist...@cardaddy.com
>> > > >
>> > > wrote:
>> > >
>> > > > Dimitris, I just tested in 5.4-beta-28 with the same exception. What
>> > > > version of tapestry-security are you using? I'm using 0.6.2? Are you
>> > > > submitting with an ajax form? I can reproduce this very easily by
>> > forcing
>> > > > my session to expire locally by advancing my computers time and then
>> > > > submitting an ajax form. It happens every single time.
>> > > >
>> > > > On Tue, Mar 31, 2015 at 1:36 PM, George Christman <
>> > > gchrist...@cardaddy.com
>> > > > >
>> > > > wrote:
>> > > >
>> > > > > I'll test it in beta-28, but until that validation bug gets
>> fixed, I
>> > > > can't
>> > > > > upgrade to it.
>> > > > >
>> > > > > On Tue, Mar 31, 2015 at 12:46 PM, Dimitris Zenios <
>> > > > > dimitris.zen...@gmail.com> wrote:
>> > > > >
>> > > > >> FYI just tested with 5.4-beta28 and I don't have such problem
>> > > > >>
>> > > > >> On Tue, Mar 31, 2015 at 5:38 PM, George Christman <
>> > > > >> gchrist...@cardaddy.com>
>> > > > >> wrote:
>> > > > >>
>> > > > >> > Hey Kalle, just checking in with you to see if you happened to
>> > have
>> > > > >> anymore
>> > > > >> > info on this issue.
>> > > > >> >
>> > > > >> > On Wed, Mar 25, 2015 at 4:05 PM, George Christman <
>> > > > >> gchrist...@cardaddy.com
>> > > > >> > >
>> > > > >> > wrote:
>> > > > >> >
>> > > > >> > > Thanks Kalle, were using 5.4-beta24
>> > > > >> > >
>> > > > >> > > On Wed, Mar 25, 2015 at 1:09 PM, Kalle Korhonen <
>> > > > >> > > kalle.o.korho...@gmail.com> wrote:
>> > > > >> > >
>> > > > >> > >> Sorry, I forgot to reply to your earlier post.
>> Fundamentally,
>> > the
>> > > >
Re: The active page name has not been specified
${message:submit-label}
${message:close-label}
On Tue, Mar 31, 2015 at 11:19 PM, George Christman
wrote:
> And your wrapping your form in a zone too? Sorry, I just want to be sure we
> are doing everything the same.
>
> On Tue, Mar 31, 2015 at 4:05 PM, Dimitris Zenios <
> dimitris.zen...@gmail.com>
> wrote:
>
> > Fedora 3.19.1-201.fc21.x86_64 #1 SMP Wed Mar 18 04:29:24 UTC 2015 x86_64
> > x86_64 x86_64 GNU/Linux
> > Java 1.8.0_40
> > Google chrome Version 41.0.2272.101 (64-bit)
> > jetty-distribution-9.2.5.v20141112
> > Tapestry 5.4-beta28
> >
> > org.tynamo
> > tapestry-security
> > 0.6.2
> >
> >
> > org.apache.tapestry
> > tapestry-core
> >
> >
> > org.apache.tapestry
> > tapestry-ioc
> >
> >
> >
> >
> > I am doing the same test as you do (Moving the clock forward). I also
> tried
> > 1.Removing the cookie
> > 2.Normal session time out by setting the time out to 1 minute (Web.xml)
> > 3.Doing session invalidate.
> >
> > All of those tests had the same result.Once the form is submitted the
> user
> > is redirected back to login page.
> >
> > On Tue, Mar 31, 2015 at 9:35 PM, Chris Poulsen
> > wrote:
> >
> > > I think I've seen the error during debugging here and there in
> beta-22...
> > > We're not using tapestry security, I can't remember if it happens when
> > I'm
> > > too slow in the javascript debugger or it is during serverside
> debugging
> > -
> > > I'll keep an eye out for it.
> > >
> > > We have a conversation moderator in play on some pages - similar to the
> > one
> > > in tynamo conversations, so requests may arrive while things are locked
> > up
> > > in either debugger - but I cannot remember if this has happened on
> pages
> > > supporting conversations.
> > >
> > > --
> > > Chris
> > >
> > > On Tue, Mar 31, 2015 at 7:52 PM, George Christman <
> > gchrist...@cardaddy.com
> > > >
> > > wrote:
> > >
> > > > Dimitris, I just tested in 5.4-beta-28 with the same exception. What
> > > > version of tapestry-security are you using? I'm using 0.6.2? Are you
> > > > submitting with an ajax form? I can reproduce this very easily by
> > forcing
> > > > my session to expire locally by advancing my computers time and then
> > > > submitting an ajax form. It happens every single time.
> > > >
> > > > On Tue, Mar 31, 2015 at 1:36 PM, George Christman <
> > > gchrist...@cardaddy.com
> > > > >
> > > > wrote:
> > > >
> > > > > I'll test it in beta-28, but until that validation bug gets fixed,
> I
> > > > can't
> > > > > upgrade to it.
> > > > >
> > > > > On Tue, Mar 31, 2015 at 12:46 PM, Dimitris Zenios <
> > > > > dimitris.zen...@gmail.com> wrote:
> > > > >
> > > > >> FYI just tested with 5.4-beta28 and I don't have such problem
> > > > >>
> > > > >> On Tue, Mar 31, 2015 at 5:38 PM, George Christman <
> > > > >> gchrist...@cardaddy.com>
> > > > >> wrote:
> > > > >>
> > > > >> > Hey Kalle, just checking in with you to see if you happened to
> > have
> > > > >> anymore
> > > > >> > info on this issue.
> > > > >> >
> > > > >> > On Wed, Mar 25, 2015 at 4:05 PM, George Christman <
> > > > >> gchrist...@cardaddy.com
> > > > >> > >
> > > > >> > wrote:
> > > > >> >
> > > > >> > > Thanks Kalle, were using 5.4-beta24
> > > > >> > >
> > > > >> > > On Wed, Mar 25, 2015 at 1:09 PM, Kalle Korhonen <
> > > > >> > > kalle.o.korho...@gmail.com> wrote:
> > > > >> > >
> > > > >> > >> Sorry, I forgot to reply to your earlier post. Fundamentally,
> > the
> > > > >> issue
> > > > >> > is
> > > > >> > >> caused by tapestry-security operating as part of the
> > > > >> httpservletrequest
> > > > >> > >> pipeline, before the active page is already set up. The
> library
> > > is
> > > > >> > >> internally setting up request globals etc. where needed but
> you
> > > may
> > > > >> be
> > > > >> > >> pushing around some shard edge there. It's also possible that
> > > some
> > > > >> > change
> > > > >> > >> in the core tapestry has caused the issue to surface. It may
> be
> > > > that
> > > > >> the
> > > > >> > >> issue happens exactly when the security library is trying to
> > deal
> > > > >> with
> > > > >> > the
> > > > >> > >> expired session. In your stack trace, you'll see that the
> > > exception
> > > > >> > >> happens
> > > > >> > >> way before the active page is being set. Just a note that you
> > > > cannot
> > > > >> > >> simply
> > > > >> > >> return a full page response to an ajax request (as you try to
> > do
> > > in
> > > > >> your
> > > > >> > >> example). What's your exact version of T5 you are using? I'll
> > see
> > > > if
> > > > >> we
> > > > >> > >> have a test for this case and try to reproduce.
> > > > >> > >>
>
Re: The active page name has not been specified
And your wrapping your form in a zone too? Sorry, I just want to be sure we are doing everything the same. On Tue, Mar 31, 2015 at 4:05 PM, Dimitris Zenios wrote: > Fedora 3.19.1-201.fc21.x86_64 #1 SMP Wed Mar 18 04:29:24 UTC 2015 x86_64 > x86_64 x86_64 GNU/Linux > Java 1.8.0_40 > Google chrome Version 41.0.2272.101 (64-bit) > jetty-distribution-9.2.5.v20141112 > Tapestry 5.4-beta28 > > org.tynamo > tapestry-security > 0.6.2 > > > org.apache.tapestry > tapestry-core > > > org.apache.tapestry > tapestry-ioc > > > > > I am doing the same test as you do (Moving the clock forward). I also tried > 1.Removing the cookie > 2.Normal session time out by setting the time out to 1 minute (Web.xml) > 3.Doing session invalidate. > > All of those tests had the same result.Once the form is submitted the user > is redirected back to login page. > > On Tue, Mar 31, 2015 at 9:35 PM, Chris Poulsen > wrote: > > > I think I've seen the error during debugging here and there in beta-22... > > We're not using tapestry security, I can't remember if it happens when > I'm > > too slow in the javascript debugger or it is during serverside debugging > - > > I'll keep an eye out for it. > > > > We have a conversation moderator in play on some pages - similar to the > one > > in tynamo conversations, so requests may arrive while things are locked > up > > in either debugger - but I cannot remember if this has happened on pages > > supporting conversations. > > > > -- > > Chris > > > > On Tue, Mar 31, 2015 at 7:52 PM, George Christman < > gchrist...@cardaddy.com > > > > > wrote: > > > > > Dimitris, I just tested in 5.4-beta-28 with the same exception. What > > > version of tapestry-security are you using? I'm using 0.6.2? Are you > > > submitting with an ajax form? I can reproduce this very easily by > forcing > > > my session to expire locally by advancing my computers time and then > > > submitting an ajax form. It happens every single time. > > > > > > On Tue, Mar 31, 2015 at 1:36 PM, George Christman < > > gchrist...@cardaddy.com > > > > > > > wrote: > > > > > > > I'll test it in beta-28, but until that validation bug gets fixed, I > > > can't > > > > upgrade to it. > > > > > > > > On Tue, Mar 31, 2015 at 12:46 PM, Dimitris Zenios < > > > > dimitris.zen...@gmail.com> wrote: > > > > > > > >> FYI just tested with 5.4-beta28 and I don't have such problem > > > >> > > > >> On Tue, Mar 31, 2015 at 5:38 PM, George Christman < > > > >> gchrist...@cardaddy.com> > > > >> wrote: > > > >> > > > >> > Hey Kalle, just checking in with you to see if you happened to > have > > > >> anymore > > > >> > info on this issue. > > > >> > > > > >> > On Wed, Mar 25, 2015 at 4:05 PM, George Christman < > > > >> gchrist...@cardaddy.com > > > >> > > > > > >> > wrote: > > > >> > > > > >> > > Thanks Kalle, were using 5.4-beta24 > > > >> > > > > > >> > > On Wed, Mar 25, 2015 at 1:09 PM, Kalle Korhonen < > > > >> > > kalle.o.korho...@gmail.com> wrote: > > > >> > > > > > >> > >> Sorry, I forgot to reply to your earlier post. Fundamentally, > the > > > >> issue > > > >> > is > > > >> > >> caused by tapestry-security operating as part of the > > > >> httpservletrequest > > > >> > >> pipeline, before the active page is already set up. The library > > is > > > >> > >> internally setting up request globals etc. where needed but you > > may > > > >> be > > > >> > >> pushing around some shard edge there. It's also possible that > > some > > > >> > change > > > >> > >> in the core tapestry has caused the issue to surface. It may be > > > that > > > >> the > > > >> > >> issue happens exactly when the security library is trying to > deal > > > >> with > > > >> > the > > > >> > >> expired session. In your stack trace, you'll see that the > > exception > > > >> > >> happens > > > >> > >> way before the active page is being set. Just a note that you > > > cannot > > > >> > >> simply > > > >> > >> return a full page response to an ajax request (as you try to > do > > in > > > >> your > > > >> > >> example). What's your exact version of T5 you are using? I'll > see > > > if > > > >> we > > > >> > >> have a test for this case and try to reproduce. > > > >> > >> > > > >> > >> Kalle > > > >> > >> > > > >> > >> On Wed, Mar 25, 2015 at 6:07 AM, George Christman < > > > >> > >> gchrist...@cardaddy.com> > > > >> > >> wrote: > > > >> > >> > > > >> > >> > So I've been able to finally reproduce this bug. I have an > ajax > > > >> form > > > >> > and > > > >> > >> > I'm using tapestry-security. When my session times out and an > > > form > > > >> > >> action > > > >> > >> > is clicked, I get the "The active page name has not been > > > specified" > > > >> > >> > exception. I found the code throwing the exception, I'm just > > not > > > >> sure > > > >> > >> why > > > >> > >> > this is happening to begin with. > > > >> > >> > > > > >> > >> > > > > >> > >> > > > >> > > > > >> > > >
Re: The active page name has not been specified
Fedora 3.19.1-201.fc21.x86_64 #1 SMP Wed Mar 18 04:29:24 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Java 1.8.0_40 Google chrome Version 41.0.2272.101 (64-bit) jetty-distribution-9.2.5.v20141112 Tapestry 5.4-beta28 org.tynamo tapestry-security 0.6.2 org.apache.tapestry tapestry-core org.apache.tapestry tapestry-ioc I am doing the same test as you do (Moving the clock forward). I also tried 1.Removing the cookie 2.Normal session time out by setting the time out to 1 minute (Web.xml) 3.Doing session invalidate. All of those tests had the same result.Once the form is submitted the user is redirected back to login page. On Tue, Mar 31, 2015 at 9:35 PM, Chris Poulsen wrote: > I think I've seen the error during debugging here and there in beta-22... > We're not using tapestry security, I can't remember if it happens when I'm > too slow in the javascript debugger or it is during serverside debugging - > I'll keep an eye out for it. > > We have a conversation moderator in play on some pages - similar to the one > in tynamo conversations, so requests may arrive while things are locked up > in either debugger - but I cannot remember if this has happened on pages > supporting conversations. > > -- > Chris > > On Tue, Mar 31, 2015 at 7:52 PM, George Christman > > wrote: > > > Dimitris, I just tested in 5.4-beta-28 with the same exception. What > > version of tapestry-security are you using? I'm using 0.6.2? Are you > > submitting with an ajax form? I can reproduce this very easily by forcing > > my session to expire locally by advancing my computers time and then > > submitting an ajax form. It happens every single time. > > > > On Tue, Mar 31, 2015 at 1:36 PM, George Christman < > gchrist...@cardaddy.com > > > > > wrote: > > > > > I'll test it in beta-28, but until that validation bug gets fixed, I > > can't > > > upgrade to it. > > > > > > On Tue, Mar 31, 2015 at 12:46 PM, Dimitris Zenios < > > > dimitris.zen...@gmail.com> wrote: > > > > > >> FYI just tested with 5.4-beta28 and I don't have such problem > > >> > > >> On Tue, Mar 31, 2015 at 5:38 PM, George Christman < > > >> gchrist...@cardaddy.com> > > >> wrote: > > >> > > >> > Hey Kalle, just checking in with you to see if you happened to have > > >> anymore > > >> > info on this issue. > > >> > > > >> > On Wed, Mar 25, 2015 at 4:05 PM, George Christman < > > >> gchrist...@cardaddy.com > > >> > > > > >> > wrote: > > >> > > > >> > > Thanks Kalle, were using 5.4-beta24 > > >> > > > > >> > > On Wed, Mar 25, 2015 at 1:09 PM, Kalle Korhonen < > > >> > > kalle.o.korho...@gmail.com> wrote: > > >> > > > > >> > >> Sorry, I forgot to reply to your earlier post. Fundamentally, the > > >> issue > > >> > is > > >> > >> caused by tapestry-security operating as part of the > > >> httpservletrequest > > >> > >> pipeline, before the active page is already set up. The library > is > > >> > >> internally setting up request globals etc. where needed but you > may > > >> be > > >> > >> pushing around some shard edge there. It's also possible that > some > > >> > change > > >> > >> in the core tapestry has caused the issue to surface. It may be > > that > > >> the > > >> > >> issue happens exactly when the security library is trying to deal > > >> with > > >> > the > > >> > >> expired session. In your stack trace, you'll see that the > exception > > >> > >> happens > > >> > >> way before the active page is being set. Just a note that you > > cannot > > >> > >> simply > > >> > >> return a full page response to an ajax request (as you try to do > in > > >> your > > >> > >> example). What's your exact version of T5 you are using? I'll see > > if > > >> we > > >> > >> have a test for this case and try to reproduce. > > >> > >> > > >> > >> Kalle > > >> > >> > > >> > >> On Wed, Mar 25, 2015 at 6:07 AM, George Christman < > > >> > >> gchrist...@cardaddy.com> > > >> > >> wrote: > > >> > >> > > >> > >> > So I've been able to finally reproduce this bug. I have an ajax > > >> form > > >> > and > > >> > >> > I'm using tapestry-security. When my session times out and an > > form > > >> > >> action > > >> > >> > is clicked, I get the "The active page name has not been > > specified" > > >> > >> > exception. I found the code throwing the exception, I'm just > not > > >> sure > > >> > >> why > > >> > >> > this is happening to begin with. > > >> > >> > > > >> > >> > > > >> > >> > > >> > > > >> > > > https://github.com/apache/tapestry-5/blob/5.4-beta-26/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/AjaxPartialResponseRendererImpl.java > > >> > >> > line 86. > > >> > >> > > > >> > >> > Shouldn't the page automatically be redirected to the login > page > > >> when > > >> > >> the > > >> > >> > user session has timed out and an action has been performed. > > >> > >> > > > >> > >> > I even tried this without any success. > > >> > >> > > > >> > >> > Object onActivate() throws E
Re: The active page name has not been specified
I think I've seen the error during debugging here and there in beta-22...
We're not using tapestry security, I can't remember if it happens when I'm
too slow in the javascript debugger or it is during serverside debugging -
I'll keep an eye out for it.
We have a conversation moderator in play on some pages - similar to the one
in tynamo conversations, so requests may arrive while things are locked up
in either debugger - but I cannot remember if this has happened on pages
supporting conversations.
--
Chris
On Tue, Mar 31, 2015 at 7:52 PM, George Christman
wrote:
> Dimitris, I just tested in 5.4-beta-28 with the same exception. What
> version of tapestry-security are you using? I'm using 0.6.2? Are you
> submitting with an ajax form? I can reproduce this very easily by forcing
> my session to expire locally by advancing my computers time and then
> submitting an ajax form. It happens every single time.
>
> On Tue, Mar 31, 2015 at 1:36 PM, George Christman >
> wrote:
>
> > I'll test it in beta-28, but until that validation bug gets fixed, I
> can't
> > upgrade to it.
> >
> > On Tue, Mar 31, 2015 at 12:46 PM, Dimitris Zenios <
> > dimitris.zen...@gmail.com> wrote:
> >
> >> FYI just tested with 5.4-beta28 and I don't have such problem
> >>
> >> On Tue, Mar 31, 2015 at 5:38 PM, George Christman <
> >> gchrist...@cardaddy.com>
> >> wrote:
> >>
> >> > Hey Kalle, just checking in with you to see if you happened to have
> >> anymore
> >> > info on this issue.
> >> >
> >> > On Wed, Mar 25, 2015 at 4:05 PM, George Christman <
> >> gchrist...@cardaddy.com
> >> > >
> >> > wrote:
> >> >
> >> > > Thanks Kalle, were using 5.4-beta24
> >> > >
> >> > > On Wed, Mar 25, 2015 at 1:09 PM, Kalle Korhonen <
> >> > > kalle.o.korho...@gmail.com> wrote:
> >> > >
> >> > >> Sorry, I forgot to reply to your earlier post. Fundamentally, the
> >> issue
> >> > is
> >> > >> caused by tapestry-security operating as part of the
> >> httpservletrequest
> >> > >> pipeline, before the active page is already set up. The library is
> >> > >> internally setting up request globals etc. where needed but you may
> >> be
> >> > >> pushing around some shard edge there. It's also possible that some
> >> > change
> >> > >> in the core tapestry has caused the issue to surface. It may be
> that
> >> the
> >> > >> issue happens exactly when the security library is trying to deal
> >> with
> >> > the
> >> > >> expired session. In your stack trace, you'll see that the exception
> >> > >> happens
> >> > >> way before the active page is being set. Just a note that you
> cannot
> >> > >> simply
> >> > >> return a full page response to an ajax request (as you try to do in
> >> your
> >> > >> example). What's your exact version of T5 you are using? I'll see
> if
> >> we
> >> > >> have a test for this case and try to reproduce.
> >> > >>
> >> > >> Kalle
> >> > >>
> >> > >> On Wed, Mar 25, 2015 at 6:07 AM, George Christman <
> >> > >> gchrist...@cardaddy.com>
> >> > >> wrote:
> >> > >>
> >> > >> > So I've been able to finally reproduce this bug. I have an ajax
> >> form
> >> > and
> >> > >> > I'm using tapestry-security. When my session times out and an
> form
> >> > >> action
> >> > >> > is clicked, I get the "The active page name has not been
> specified"
> >> > >> > exception. I found the code throwing the exception, I'm just not
> >> sure
> >> > >> why
> >> > >> > this is happening to begin with.
> >> > >> >
> >> > >> >
> >> > >>
> >> >
> >>
> https://github.com/apache/tapestry-5/blob/5.4-beta-26/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/AjaxPartialResponseRendererImpl.java
> >> > >> > line 86.
> >> > >> >
> >> > >> > Shouldn't the page automatically be redirected to the login page
> >> when
> >> > >> the
> >> > >> > user session has timed out and an action has been performed.
> >> > >> >
> >> > >> > I even tried this without any success.
> >> > >> >
> >> > >> > Object onActivate() throws Exception {
> >> > >> > if (request.isRequestedSessionIdValid()) {
> >> > >> > //some code
> >> > >> > }
> >> > >> > return Login.class;
> >> > >> > }
> >> > >> >
> >> > >> > Any thoughts on how to repair this issue?
> >> > >> >
> >> > >> > On Thu, Mar 19, 2015 at 12:54 PM, George Christman <
> >> > >> > gchrist...@cardaddy.com>
> >> > >> > wrote:
> >> > >> >
> >> > >> > > Could someone help me to understand this exception? I'm using
> Tap
> >> > 5.4
> >> > >> and
> >> > >> > > I've been seeing this quite often, but can't seem to reproduce
> >> it.
> >> > >> > >
> >> > >> > > The active page name has not been
> >> > >> > > specified.org.apache.tapestry5.ioc.internal.OperationException:
> >> The
> >> > >> > active
> >> > >> > > page name has not been specified. at
> >> > >> > >
> >> > >> >
> >> > >>
> >> >
> >>
> org.apache.tapestry5.ioc.internal.OperationTrackerImpl.logAndRethrow(OperationTrackerImpl.java:184)
> >> > >> > > at
> >> > >> > >
> >> > >> >
> >> > >>
> >> >
> >>
> org.apache.tapestry5.ioc.internal.Ope
Re: The active page name has not been specified
Dimitris, I just tested in 5.4-beta-28 with the same exception. What
version of tapestry-security are you using? I'm using 0.6.2? Are you
submitting with an ajax form? I can reproduce this very easily by forcing
my session to expire locally by advancing my computers time and then
submitting an ajax form. It happens every single time.
On Tue, Mar 31, 2015 at 1:36 PM, George Christman
wrote:
> I'll test it in beta-28, but until that validation bug gets fixed, I can't
> upgrade to it.
>
> On Tue, Mar 31, 2015 at 12:46 PM, Dimitris Zenios <
> dimitris.zen...@gmail.com> wrote:
>
>> FYI just tested with 5.4-beta28 and I don't have such problem
>>
>> On Tue, Mar 31, 2015 at 5:38 PM, George Christman <
>> gchrist...@cardaddy.com>
>> wrote:
>>
>> > Hey Kalle, just checking in with you to see if you happened to have
>> anymore
>> > info on this issue.
>> >
>> > On Wed, Mar 25, 2015 at 4:05 PM, George Christman <
>> gchrist...@cardaddy.com
>> > >
>> > wrote:
>> >
>> > > Thanks Kalle, were using 5.4-beta24
>> > >
>> > > On Wed, Mar 25, 2015 at 1:09 PM, Kalle Korhonen <
>> > > kalle.o.korho...@gmail.com> wrote:
>> > >
>> > >> Sorry, I forgot to reply to your earlier post. Fundamentally, the
>> issue
>> > is
>> > >> caused by tapestry-security operating as part of the
>> httpservletrequest
>> > >> pipeline, before the active page is already set up. The library is
>> > >> internally setting up request globals etc. where needed but you may
>> be
>> > >> pushing around some shard edge there. It's also possible that some
>> > change
>> > >> in the core tapestry has caused the issue to surface. It may be that
>> the
>> > >> issue happens exactly when the security library is trying to deal
>> with
>> > the
>> > >> expired session. In your stack trace, you'll see that the exception
>> > >> happens
>> > >> way before the active page is being set. Just a note that you cannot
>> > >> simply
>> > >> return a full page response to an ajax request (as you try to do in
>> your
>> > >> example). What's your exact version of T5 you are using? I'll see if
>> we
>> > >> have a test for this case and try to reproduce.
>> > >>
>> > >> Kalle
>> > >>
>> > >> On Wed, Mar 25, 2015 at 6:07 AM, George Christman <
>> > >> gchrist...@cardaddy.com>
>> > >> wrote:
>> > >>
>> > >> > So I've been able to finally reproduce this bug. I have an ajax
>> form
>> > and
>> > >> > I'm using tapestry-security. When my session times out and an form
>> > >> action
>> > >> > is clicked, I get the "The active page name has not been specified"
>> > >> > exception. I found the code throwing the exception, I'm just not
>> sure
>> > >> why
>> > >> > this is happening to begin with.
>> > >> >
>> > >> >
>> > >>
>> >
>> https://github.com/apache/tapestry-5/blob/5.4-beta-26/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/AjaxPartialResponseRendererImpl.java
>> > >> > line 86.
>> > >> >
>> > >> > Shouldn't the page automatically be redirected to the login page
>> when
>> > >> the
>> > >> > user session has timed out and an action has been performed.
>> > >> >
>> > >> > I even tried this without any success.
>> > >> >
>> > >> > Object onActivate() throws Exception {
>> > >> > if (request.isRequestedSessionIdValid()) {
>> > >> > //some code
>> > >> > }
>> > >> > return Login.class;
>> > >> > }
>> > >> >
>> > >> > Any thoughts on how to repair this issue?
>> > >> >
>> > >> > On Thu, Mar 19, 2015 at 12:54 PM, George Christman <
>> > >> > gchrist...@cardaddy.com>
>> > >> > wrote:
>> > >> >
>> > >> > > Could someone help me to understand this exception? I'm using Tap
>> > 5.4
>> > >> and
>> > >> > > I've been seeing this quite often, but can't seem to reproduce
>> it.
>> > >> > >
>> > >> > > The active page name has not been
>> > >> > > specified.org.apache.tapestry5.ioc.internal.OperationException:
>> The
>> > >> > active
>> > >> > > page name has not been specified. at
>> > >> > >
>> > >> >
>> > >>
>> >
>> org.apache.tapestry5.ioc.internal.OperationTrackerImpl.logAndRethrow(OperationTrackerImpl.java:184)
>> > >> > > at
>> > >> > >
>> > >> >
>> > >>
>> >
>> org.apache.tapestry5.ioc.internal.OperationTrackerImpl.perform(OperationTrackerImpl.java:118)
>> > >> > > at
>> > >> > >
>> > >> >
>> > >>
>> >
>> org.apache.tapestry5.ioc.internal.PerThreadOperationTracker.perform(PerThreadOperationTracker.java:84)
>> > >> > > at
>> > >> > >
>> > >> >
>> > >>
>> >
>> org.apache.tapestry5.ioc.internal.RegistryImpl.perform(RegistryImpl.java:1264)
>> > >> > > at
>> > >> > >
>> > >> >
>> > >>
>> >
>> org.apache.tapestry5.internal.services.DeferredResponseRenderer.invokeQueuedRenderer(DeferredResponseRenderer.java:73)
>> > >> > > at
>> > >> > >
>> > >> >
>> > >>
>> >
>> org.apache.tapestry5.internal.services.DeferredResponseRenderer.handleComponentEvent(DeferredResponseRenderer.java:47)
>> > >> > > at
>> > $ComponentRequestHandler_18c715615aaee.handleComponentEvent(Unknown
>> > >> > > Source) at
>> > >> > >
>> > >> >
>> > >>
>> >
>> org.apa
Re: The active page name has not been specified
I'll test it in beta-28, but until that validation bug gets fixed, I can't
upgrade to it.
On Tue, Mar 31, 2015 at 12:46 PM, Dimitris Zenios wrote:
> FYI just tested with 5.4-beta28 and I don't have such problem
>
> On Tue, Mar 31, 2015 at 5:38 PM, George Christman >
> wrote:
>
> > Hey Kalle, just checking in with you to see if you happened to have
> anymore
> > info on this issue.
> >
> > On Wed, Mar 25, 2015 at 4:05 PM, George Christman <
> gchrist...@cardaddy.com
> > >
> > wrote:
> >
> > > Thanks Kalle, were using 5.4-beta24
> > >
> > > On Wed, Mar 25, 2015 at 1:09 PM, Kalle Korhonen <
> > > kalle.o.korho...@gmail.com> wrote:
> > >
> > >> Sorry, I forgot to reply to your earlier post. Fundamentally, the
> issue
> > is
> > >> caused by tapestry-security operating as part of the
> httpservletrequest
> > >> pipeline, before the active page is already set up. The library is
> > >> internally setting up request globals etc. where needed but you may be
> > >> pushing around some shard edge there. It's also possible that some
> > change
> > >> in the core tapestry has caused the issue to surface. It may be that
> the
> > >> issue happens exactly when the security library is trying to deal with
> > the
> > >> expired session. In your stack trace, you'll see that the exception
> > >> happens
> > >> way before the active page is being set. Just a note that you cannot
> > >> simply
> > >> return a full page response to an ajax request (as you try to do in
> your
> > >> example). What's your exact version of T5 you are using? I'll see if
> we
> > >> have a test for this case and try to reproduce.
> > >>
> > >> Kalle
> > >>
> > >> On Wed, Mar 25, 2015 at 6:07 AM, George Christman <
> > >> gchrist...@cardaddy.com>
> > >> wrote:
> > >>
> > >> > So I've been able to finally reproduce this bug. I have an ajax form
> > and
> > >> > I'm using tapestry-security. When my session times out and an form
> > >> action
> > >> > is clicked, I get the "The active page name has not been specified"
> > >> > exception. I found the code throwing the exception, I'm just not
> sure
> > >> why
> > >> > this is happening to begin with.
> > >> >
> > >> >
> > >>
> >
> https://github.com/apache/tapestry-5/blob/5.4-beta-26/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/AjaxPartialResponseRendererImpl.java
> > >> > line 86.
> > >> >
> > >> > Shouldn't the page automatically be redirected to the login page
> when
> > >> the
> > >> > user session has timed out and an action has been performed.
> > >> >
> > >> > I even tried this without any success.
> > >> >
> > >> > Object onActivate() throws Exception {
> > >> > if (request.isRequestedSessionIdValid()) {
> > >> > //some code
> > >> > }
> > >> > return Login.class;
> > >> > }
> > >> >
> > >> > Any thoughts on how to repair this issue?
> > >> >
> > >> > On Thu, Mar 19, 2015 at 12:54 PM, George Christman <
> > >> > gchrist...@cardaddy.com>
> > >> > wrote:
> > >> >
> > >> > > Could someone help me to understand this exception? I'm using Tap
> > 5.4
> > >> and
> > >> > > I've been seeing this quite often, but can't seem to reproduce it.
> > >> > >
> > >> > > The active page name has not been
> > >> > > specified.org.apache.tapestry5.ioc.internal.OperationException:
> The
> > >> > active
> > >> > > page name has not been specified. at
> > >> > >
> > >> >
> > >>
> >
> org.apache.tapestry5.ioc.internal.OperationTrackerImpl.logAndRethrow(OperationTrackerImpl.java:184)
> > >> > > at
> > >> > >
> > >> >
> > >>
> >
> org.apache.tapestry5.ioc.internal.OperationTrackerImpl.perform(OperationTrackerImpl.java:118)
> > >> > > at
> > >> > >
> > >> >
> > >>
> >
> org.apache.tapestry5.ioc.internal.PerThreadOperationTracker.perform(PerThreadOperationTracker.java:84)
> > >> > > at
> > >> > >
> > >> >
> > >>
> >
> org.apache.tapestry5.ioc.internal.RegistryImpl.perform(RegistryImpl.java:1264)
> > >> > > at
> > >> > >
> > >> >
> > >>
> >
> org.apache.tapestry5.internal.services.DeferredResponseRenderer.invokeQueuedRenderer(DeferredResponseRenderer.java:73)
> > >> > > at
> > >> > >
> > >> >
> > >>
> >
> org.apache.tapestry5.internal.services.DeferredResponseRenderer.handleComponentEvent(DeferredResponseRenderer.java:47)
> > >> > > at
> > $ComponentRequestHandler_18c715615aaee.handleComponentEvent(Unknown
> > >> > > Source) at
> > >> > >
> > >> >
> > >>
> >
> org.apache.tapestry5.services.InitializeActivePageName.handleComponentEvent(InitializeActivePageName.java:39)
> > >> > > at
> > $ComponentRequestHandler_18c715615aaee.handleComponentEvent(Unknown
> > >> > > Source) at
> > >> > >
> > >> >
> > >>
> >
> org.apache.tapestry5.internal.services.ProductionModeUnknownComponentFilter.handleComponentEvent(ProductionModeUnknownComponentFilter.java:50)
> > >> > > at
> > $ComponentRequestHandler_18c715615aaee.handleComponentEvent(Unknown
> > >> > > Source) at
> > >> > >
> > >> >
> > >>
> >
> org.apache.tapestry5.internal.services.RequestOperationTracker$1.perform(RequestOp
Re: The active page name has not been specified
FYI just tested with 5.4-beta28 and I don't have such problem
On Tue, Mar 31, 2015 at 5:38 PM, George Christman
wrote:
> Hey Kalle, just checking in with you to see if you happened to have anymore
> info on this issue.
>
> On Wed, Mar 25, 2015 at 4:05 PM, George Christman >
> wrote:
>
> > Thanks Kalle, were using 5.4-beta24
> >
> > On Wed, Mar 25, 2015 at 1:09 PM, Kalle Korhonen <
> > kalle.o.korho...@gmail.com> wrote:
> >
> >> Sorry, I forgot to reply to your earlier post. Fundamentally, the issue
> is
> >> caused by tapestry-security operating as part of the httpservletrequest
> >> pipeline, before the active page is already set up. The library is
> >> internally setting up request globals etc. where needed but you may be
> >> pushing around some shard edge there. It's also possible that some
> change
> >> in the core tapestry has caused the issue to surface. It may be that the
> >> issue happens exactly when the security library is trying to deal with
> the
> >> expired session. In your stack trace, you'll see that the exception
> >> happens
> >> way before the active page is being set. Just a note that you cannot
> >> simply
> >> return a full page response to an ajax request (as you try to do in your
> >> example). What's your exact version of T5 you are using? I'll see if we
> >> have a test for this case and try to reproduce.
> >>
> >> Kalle
> >>
> >> On Wed, Mar 25, 2015 at 6:07 AM, George Christman <
> >> gchrist...@cardaddy.com>
> >> wrote:
> >>
> >> > So I've been able to finally reproduce this bug. I have an ajax form
> and
> >> > I'm using tapestry-security. When my session times out and an form
> >> action
> >> > is clicked, I get the "The active page name has not been specified"
> >> > exception. I found the code throwing the exception, I'm just not sure
> >> why
> >> > this is happening to begin with.
> >> >
> >> >
> >>
> https://github.com/apache/tapestry-5/blob/5.4-beta-26/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/AjaxPartialResponseRendererImpl.java
> >> > line 86.
> >> >
> >> > Shouldn't the page automatically be redirected to the login page when
> >> the
> >> > user session has timed out and an action has been performed.
> >> >
> >> > I even tried this without any success.
> >> >
> >> > Object onActivate() throws Exception {
> >> > if (request.isRequestedSessionIdValid()) {
> >> > //some code
> >> > }
> >> > return Login.class;
> >> > }
> >> >
> >> > Any thoughts on how to repair this issue?
> >> >
> >> > On Thu, Mar 19, 2015 at 12:54 PM, George Christman <
> >> > gchrist...@cardaddy.com>
> >> > wrote:
> >> >
> >> > > Could someone help me to understand this exception? I'm using Tap
> 5.4
> >> and
> >> > > I've been seeing this quite often, but can't seem to reproduce it.
> >> > >
> >> > > The active page name has not been
> >> > > specified.org.apache.tapestry5.ioc.internal.OperationException: The
> >> > active
> >> > > page name has not been specified. at
> >> > >
> >> >
> >>
> org.apache.tapestry5.ioc.internal.OperationTrackerImpl.logAndRethrow(OperationTrackerImpl.java:184)
> >> > > at
> >> > >
> >> >
> >>
> org.apache.tapestry5.ioc.internal.OperationTrackerImpl.perform(OperationTrackerImpl.java:118)
> >> > > at
> >> > >
> >> >
> >>
> org.apache.tapestry5.ioc.internal.PerThreadOperationTracker.perform(PerThreadOperationTracker.java:84)
> >> > > at
> >> > >
> >> >
> >>
> org.apache.tapestry5.ioc.internal.RegistryImpl.perform(RegistryImpl.java:1264)
> >> > > at
> >> > >
> >> >
> >>
> org.apache.tapestry5.internal.services.DeferredResponseRenderer.invokeQueuedRenderer(DeferredResponseRenderer.java:73)
> >> > > at
> >> > >
> >> >
> >>
> org.apache.tapestry5.internal.services.DeferredResponseRenderer.handleComponentEvent(DeferredResponseRenderer.java:47)
> >> > > at
> $ComponentRequestHandler_18c715615aaee.handleComponentEvent(Unknown
> >> > > Source) at
> >> > >
> >> >
> >>
> org.apache.tapestry5.services.InitializeActivePageName.handleComponentEvent(InitializeActivePageName.java:39)
> >> > > at
> $ComponentRequestHandler_18c715615aaee.handleComponentEvent(Unknown
> >> > > Source) at
> >> > >
> >> >
> >>
> org.apache.tapestry5.internal.services.ProductionModeUnknownComponentFilter.handleComponentEvent(ProductionModeUnknownComponentFilter.java:50)
> >> > > at
> $ComponentRequestHandler_18c715615aaee.handleComponentEvent(Unknown
> >> > > Source) at
> >> > >
> >> >
> >>
> org.apache.tapestry5.internal.services.RequestOperationTracker$1.perform(RequestOperationTracker.java:55)
> >> > > at
> >> > >
> >> >
> >>
> org.apache.tapestry5.internal.services.RequestOperationTracker$1.perform(RequestOperationTracker.java:52)
> >> > > at
> >> > >
> >> >
> >>
> org.apache.tapestry5.ioc.internal.OperationTrackerImpl.perform(OperationTrackerImpl.java:110)
> >> > > at
> >> > >
> >> >
> >>
> org.apache.tapestry5.ioc.internal.PerThreadOperationTracker.perform(PerThreadOperationTracker.java:84)
> >> > > at
> >> > >
> >> >
> >>
> org.apache.tapes
Re: The active page name has not been specified
Hey Kalle, just checking in with you to see if you happened to have anymore
info on this issue.
On Wed, Mar 25, 2015 at 4:05 PM, George Christman
wrote:
> Thanks Kalle, were using 5.4-beta24
>
> On Wed, Mar 25, 2015 at 1:09 PM, Kalle Korhonen <
> kalle.o.korho...@gmail.com> wrote:
>
>> Sorry, I forgot to reply to your earlier post. Fundamentally, the issue is
>> caused by tapestry-security operating as part of the httpservletrequest
>> pipeline, before the active page is already set up. The library is
>> internally setting up request globals etc. where needed but you may be
>> pushing around some shard edge there. It's also possible that some change
>> in the core tapestry has caused the issue to surface. It may be that the
>> issue happens exactly when the security library is trying to deal with the
>> expired session. In your stack trace, you'll see that the exception
>> happens
>> way before the active page is being set. Just a note that you cannot
>> simply
>> return a full page response to an ajax request (as you try to do in your
>> example). What's your exact version of T5 you are using? I'll see if we
>> have a test for this case and try to reproduce.
>>
>> Kalle
>>
>> On Wed, Mar 25, 2015 at 6:07 AM, George Christman <
>> gchrist...@cardaddy.com>
>> wrote:
>>
>> > So I've been able to finally reproduce this bug. I have an ajax form and
>> > I'm using tapestry-security. When my session times out and an form
>> action
>> > is clicked, I get the "The active page name has not been specified"
>> > exception. I found the code throwing the exception, I'm just not sure
>> why
>> > this is happening to begin with.
>> >
>> >
>> https://github.com/apache/tapestry-5/blob/5.4-beta-26/tapestry-core/src/main/java/org/apache/tapestry5/internal/services/AjaxPartialResponseRendererImpl.java
>> > line 86.
>> >
>> > Shouldn't the page automatically be redirected to the login page when
>> the
>> > user session has timed out and an action has been performed.
>> >
>> > I even tried this without any success.
>> >
>> > Object onActivate() throws Exception {
>> > if (request.isRequestedSessionIdValid()) {
>> > //some code
>> > }
>> > return Login.class;
>> > }
>> >
>> > Any thoughts on how to repair this issue?
>> >
>> > On Thu, Mar 19, 2015 at 12:54 PM, George Christman <
>> > gchrist...@cardaddy.com>
>> > wrote:
>> >
>> > > Could someone help me to understand this exception? I'm using Tap 5.4
>> and
>> > > I've been seeing this quite often, but can't seem to reproduce it.
>> > >
>> > > The active page name has not been
>> > > specified.org.apache.tapestry5.ioc.internal.OperationException: The
>> > active
>> > > page name has not been specified. at
>> > >
>> >
>> org.apache.tapestry5.ioc.internal.OperationTrackerImpl.logAndRethrow(OperationTrackerImpl.java:184)
>> > > at
>> > >
>> >
>> org.apache.tapestry5.ioc.internal.OperationTrackerImpl.perform(OperationTrackerImpl.java:118)
>> > > at
>> > >
>> >
>> org.apache.tapestry5.ioc.internal.PerThreadOperationTracker.perform(PerThreadOperationTracker.java:84)
>> > > at
>> > >
>> >
>> org.apache.tapestry5.ioc.internal.RegistryImpl.perform(RegistryImpl.java:1264)
>> > > at
>> > >
>> >
>> org.apache.tapestry5.internal.services.DeferredResponseRenderer.invokeQueuedRenderer(DeferredResponseRenderer.java:73)
>> > > at
>> > >
>> >
>> org.apache.tapestry5.internal.services.DeferredResponseRenderer.handleComponentEvent(DeferredResponseRenderer.java:47)
>> > > at $ComponentRequestHandler_18c715615aaee.handleComponentEvent(Unknown
>> > > Source) at
>> > >
>> >
>> org.apache.tapestry5.services.InitializeActivePageName.handleComponentEvent(InitializeActivePageName.java:39)
>> > > at $ComponentRequestHandler_18c715615aaee.handleComponentEvent(Unknown
>> > > Source) at
>> > >
>> >
>> org.apache.tapestry5.internal.services.ProductionModeUnknownComponentFilter.handleComponentEvent(ProductionModeUnknownComponentFilter.java:50)
>> > > at $ComponentRequestHandler_18c715615aaee.handleComponentEvent(Unknown
>> > > Source) at
>> > >
>> >
>> org.apache.tapestry5.internal.services.RequestOperationTracker$1.perform(RequestOperationTracker.java:55)
>> > > at
>> > >
>> >
>> org.apache.tapestry5.internal.services.RequestOperationTracker$1.perform(RequestOperationTracker.java:52)
>> > > at
>> > >
>> >
>> org.apache.tapestry5.ioc.internal.OperationTrackerImpl.perform(OperationTrackerImpl.java:110)
>> > > at
>> > >
>> >
>> org.apache.tapestry5.ioc.internal.PerThreadOperationTracker.perform(PerThreadOperationTracker.java:84)
>> > > at
>> > >
>> >
>> org.apache.tapestry5.ioc.internal.RegistryImpl.perform(RegistryImpl.java:1264)
>> > > at
>> > >
>> >
>> org.apache.tapestry5.internal.services.RequestOperationTracker.handleComponentEvent(RequestOperationTracker.java:47)
>> > > at $ComponentRequestHandler_18c715615aaee.handleComponentEvent(Unknown
>> > > Source) at
>> > >
>> >
>> org.tynamo.security.SecurityComponentRequestFilter.handleComponentEvent(SecurityComponentRequestFilt
Re: JS conflict
On Tue, 31 Mar 2015 01:37:58 -0300, Cheng Zhang wrote: Thanks for reminding me Thiago. I do not know if my company will use the non-stable version of Tapestry in production. It is stable very much. :) -- Thiago H. de Paula Figueiredo Tapestry, Java and Hibernate consultant and developer http://machina.com.br - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
