You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Martin Makundi <ma...@koodaripalvelut.com> on 2009/06/16 09:58:00 UTC
Login page crashes if old bookmark
Hi!
I get the following error when users come to the login page using a
stateful bookmark:
2009-06-16 10:11:52,861 43237745 [btpool0-115] ERROR RequestCycle -
component loginForm not found on page
Any tricks how this can be avoided?
**
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Login page crashes if old bookmark
Posted by Igor Vaynberg <ig...@gmail.com>.
i have no idea. use something like liveheaders to make sure you are
consistently getting the same session id.
there is more info in HttpsRequestCycleProcessor javadoc.
-igor
On Tue, Jun 16, 2009 at 1:27 PM, Martin
Makundi<ma...@koodaripalvelut.com> wrote:
>> this has nothing to do with how many servers you are running
>
> Does it matter that Apache handles the https and proxies it as plain
> http to jetty?
>
> **
> Martin
>
>>
>> -igor
>>
>> On Tue, Jun 16, 2009 at 12:56 PM, Martin
>> Makundi<ma...@koodaripalvelut.com> wrote:
>>>> as far as wicket is concerned it does the best it can. when the
>>>> session is gone we have no state information at all and the only thing
>>>> we can do is display the page expired page. what exactly is
>>>> "unprofessional" about this.
>>>
>>> Well.. this crash :) It is not very 'graceful', maybe better wording
>>> than professionality....
>>>
>>>> btw, is your login page https? this may be caused by the fact that you
>>>> will have two different session ids: one secure and one not secure.
>>>
>>> This is actually true... however I have a single jetty listening to
>>> :8080 so I would presume it sees a single session.
>>>
>>> **
>>> Martin
>>>
>>>> On Tue, Jun 16, 2009 at 12:21 PM, Martin
>>>> Makundi<ma...@koodaripalvelut.com> wrote:
>>>>> I have a feeling this has something to do with the littlebit
>>>>> 'unprofessional' way of wicket's dealing with session expiration on
>>>>> stateful pages. Wicket sort of deals with session expiration like if
>>>>> it was a fatal state.. while it is just daily bloody normal ;)
>>>>> Anyways... I will look into this, it's bugged me for 1 year now and I
>>>>> have managed to override it but not solve it.
>>>>>
>>>>> **
>>>>> Martin
>>>>>
>>>>> 2009/6/16 Igor Vaynberg <ig...@gmail.com>:
>>>>>> so the curiosity is why is wicket trying to submit the loginform to
>>>>>> the mainpage? i dont think i have seen anything like this before. if
>>>>>> you can find a way to reproduce it we will be happy to fix it.
>>>>>>
>>>>>> -igor
>>>>>>
>>>>>> On Tue, Jun 16, 2009 at 11:54 AM, Martin
>>>>>> Makundi<ma...@koodaripalvelut.com> wrote:
>>>>>>> No. MainPage is the page the user has probably bookmarked or something.. it
>>>>>>> is the page after successful login.
>>>>>>> **
>>>>>>> Martin
>>>>>>>
>>>>>>> 2009/6/16 Igor Vaynberg <ig...@gmail.com>
>>>>>>>
>>>>>>>> is your LoginPage the com.domain.view.application.MainPage ?
>>>>>>>>
>>>>>>>> -igor
>>>>>>>>
>>>>>>>> On Tue, Jun 16, 2009 at 9:54 AM, Martin
>>>>>>>> Makundi<ma...@koodaripalvelut.com> wrote:
>>>>>>>> > I am not actually sure how to repeat this bug, this is what I see on
>>>>>>>> > the production log.
>>>>>>>> >
>>>>>>>> > **
>>>>>>>> > Martin
>>>>>>>> >
>>>>>>>> > 2009/6/16 Igor Vaynberg <ig...@gmail.com>:
>>>>>>>> >> IFormSubmitListener? so this happens when you submit the login page?
>>>>>>>> >>
>>>>>>>> >> -igor
>>>>>>>> >>
>>>>>>>> >> On Tue, Jun 16, 2009 at 9:30 AM, Martin
>>>>>>>> >> Makundi<ma...@koodaripalvelut.com> wrote:
>>>>>>>> >>>> IIRC, for this purpose I had written a separate expired page but I had
>>>>>>>> >>>> thrown a new restartresponseexception(LoginPage.class) which was
>>>>>>>> working
>>>>>>>> >>>> fine with wicket 1.3.4.
>>>>>>>> >>>
>>>>>>>> >>> So is there a bug with the pageparameters for a stateful page? They
>>>>>>>> >>> should be thrown away when pageExpired occurs (this happens
>>>>>>>> >>> automatically with restartresponseexception?)?
>>>>>>>> >>>
>>>>>>>> >>> Here is some more of the stack:
>>>>>>>> >
>>>>>>>> > ---------------------------------------------------------------------
>>>>>>>> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>>>>> > For additional commands, e-mail: users-help@wicket.apache.org
>>>>>>>> >
>>>>>>>> >
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Login page crashes if old bookmark
Posted by Martin Makundi <ma...@koodaripalvelut.com>.
> this has nothing to do with how many servers you are running
Does it matter that Apache handles the https and proxies it as plain
http to jetty?
**
Martin
>
> -igor
>
> On Tue, Jun 16, 2009 at 12:56 PM, Martin
> Makundi<ma...@koodaripalvelut.com> wrote:
>>> as far as wicket is concerned it does the best it can. when the
>>> session is gone we have no state information at all and the only thing
>>> we can do is display the page expired page. what exactly is
>>> "unprofessional" about this.
>>
>> Well.. this crash :) It is not very 'graceful', maybe better wording
>> than professionality....
>>
>>> btw, is your login page https? this may be caused by the fact that you
>>> will have two different session ids: one secure and one not secure.
>>
>> This is actually true... however I have a single jetty listening to
>> :8080 so I would presume it sees a single session.
>>
>> **
>> Martin
>>
>>> On Tue, Jun 16, 2009 at 12:21 PM, Martin
>>> Makundi<ma...@koodaripalvelut.com> wrote:
>>>> I have a feeling this has something to do with the littlebit
>>>> 'unprofessional' way of wicket's dealing with session expiration on
>>>> stateful pages. Wicket sort of deals with session expiration like if
>>>> it was a fatal state.. while it is just daily bloody normal ;)
>>>> Anyways... I will look into this, it's bugged me for 1 year now and I
>>>> have managed to override it but not solve it.
>>>>
>>>> **
>>>> Martin
>>>>
>>>> 2009/6/16 Igor Vaynberg <ig...@gmail.com>:
>>>>> so the curiosity is why is wicket trying to submit the loginform to
>>>>> the mainpage? i dont think i have seen anything like this before. if
>>>>> you can find a way to reproduce it we will be happy to fix it.
>>>>>
>>>>> -igor
>>>>>
>>>>> On Tue, Jun 16, 2009 at 11:54 AM, Martin
>>>>> Makundi<ma...@koodaripalvelut.com> wrote:
>>>>>> No. MainPage is the page the user has probably bookmarked or something.. it
>>>>>> is the page after successful login.
>>>>>> **
>>>>>> Martin
>>>>>>
>>>>>> 2009/6/16 Igor Vaynberg <ig...@gmail.com>
>>>>>>
>>>>>>> is your LoginPage the com.domain.view.application.MainPage ?
>>>>>>>
>>>>>>> -igor
>>>>>>>
>>>>>>> On Tue, Jun 16, 2009 at 9:54 AM, Martin
>>>>>>> Makundi<ma...@koodaripalvelut.com> wrote:
>>>>>>> > I am not actually sure how to repeat this bug, this is what I see on
>>>>>>> > the production log.
>>>>>>> >
>>>>>>> > **
>>>>>>> > Martin
>>>>>>> >
>>>>>>> > 2009/6/16 Igor Vaynberg <ig...@gmail.com>:
>>>>>>> >> IFormSubmitListener? so this happens when you submit the login page?
>>>>>>> >>
>>>>>>> >> -igor
>>>>>>> >>
>>>>>>> >> On Tue, Jun 16, 2009 at 9:30 AM, Martin
>>>>>>> >> Makundi<ma...@koodaripalvelut.com> wrote:
>>>>>>> >>>> IIRC, for this purpose I had written a separate expired page but I had
>>>>>>> >>>> thrown a new restartresponseexception(LoginPage.class) which was
>>>>>>> working
>>>>>>> >>>> fine with wicket 1.3.4.
>>>>>>> >>>
>>>>>>> >>> So is there a bug with the pageparameters for a stateful page? They
>>>>>>> >>> should be thrown away when pageExpired occurs (this happens
>>>>>>> >>> automatically with restartresponseexception?)?
>>>>>>> >>>
>>>>>>> >>> Here is some more of the stack:
>>>>>>> >
>>>>>>> > ---------------------------------------------------------------------
>>>>>>> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>>>> > For additional commands, e-mail: users-help@wicket.apache.org
>>>>>>> >
>>>>>>> >
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Login page crashes if old bookmark
Posted by Igor Vaynberg <ig...@gmail.com>.
this has nothing to do with how many servers you are running
most containers will create a new sessionid for https requests and
mark that cookie as secure - so it cannot be hijacked.
so your app sees one session for http urls and another for https urls
- all without the application actually knowing anything about it.
a possible solution can be to force session creation on first access
to http url. there was another thread about this very recently, you
might want to search for it.
-igor
On Tue, Jun 16, 2009 at 12:56 PM, Martin
Makundi<ma...@koodaripalvelut.com> wrote:
>> as far as wicket is concerned it does the best it can. when the
>> session is gone we have no state information at all and the only thing
>> we can do is display the page expired page. what exactly is
>> "unprofessional" about this.
>
> Well.. this crash :) It is not very 'graceful', maybe better wording
> than professionality....
>
>> btw, is your login page https? this may be caused by the fact that you
>> will have two different session ids: one secure and one not secure.
>
> This is actually true... however I have a single jetty listening to
> :8080 so I would presume it sees a single session.
>
> **
> Martin
>
>> On Tue, Jun 16, 2009 at 12:21 PM, Martin
>> Makundi<ma...@koodaripalvelut.com> wrote:
>>> I have a feeling this has something to do with the littlebit
>>> 'unprofessional' way of wicket's dealing with session expiration on
>>> stateful pages. Wicket sort of deals with session expiration like if
>>> it was a fatal state.. while it is just daily bloody normal ;)
>>> Anyways... I will look into this, it's bugged me for 1 year now and I
>>> have managed to override it but not solve it.
>>>
>>> **
>>> Martin
>>>
>>> 2009/6/16 Igor Vaynberg <ig...@gmail.com>:
>>>> so the curiosity is why is wicket trying to submit the loginform to
>>>> the mainpage? i dont think i have seen anything like this before. if
>>>> you can find a way to reproduce it we will be happy to fix it.
>>>>
>>>> -igor
>>>>
>>>> On Tue, Jun 16, 2009 at 11:54 AM, Martin
>>>> Makundi<ma...@koodaripalvelut.com> wrote:
>>>>> No. MainPage is the page the user has probably bookmarked or something.. it
>>>>> is the page after successful login.
>>>>> **
>>>>> Martin
>>>>>
>>>>> 2009/6/16 Igor Vaynberg <ig...@gmail.com>
>>>>>
>>>>>> is your LoginPage the com.domain.view.application.MainPage ?
>>>>>>
>>>>>> -igor
>>>>>>
>>>>>> On Tue, Jun 16, 2009 at 9:54 AM, Martin
>>>>>> Makundi<ma...@koodaripalvelut.com> wrote:
>>>>>> > I am not actually sure how to repeat this bug, this is what I see on
>>>>>> > the production log.
>>>>>> >
>>>>>> > **
>>>>>> > Martin
>>>>>> >
>>>>>> > 2009/6/16 Igor Vaynberg <ig...@gmail.com>:
>>>>>> >> IFormSubmitListener? so this happens when you submit the login page?
>>>>>> >>
>>>>>> >> -igor
>>>>>> >>
>>>>>> >> On Tue, Jun 16, 2009 at 9:30 AM, Martin
>>>>>> >> Makundi<ma...@koodaripalvelut.com> wrote:
>>>>>> >>>> IIRC, for this purpose I had written a separate expired page but I had
>>>>>> >>>> thrown a new restartresponseexception(LoginPage.class) which was
>>>>>> working
>>>>>> >>>> fine with wicket 1.3.4.
>>>>>> >>>
>>>>>> >>> So is there a bug with the pageparameters for a stateful page? They
>>>>>> >>> should be thrown away when pageExpired occurs (this happens
>>>>>> >>> automatically with restartresponseexception?)?
>>>>>> >>>
>>>>>> >>> Here is some more of the stack:
>>>>>> >
>>>>>> > ---------------------------------------------------------------------
>>>>>> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>>> > For additional commands, e-mail: users-help@wicket.apache.org
>>>>>> >
>>>>>> >
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Login page crashes if old bookmark
Posted by Martin Makundi <ma...@koodaripalvelut.com>.
> as far as wicket is concerned it does the best it can. when the
> session is gone we have no state information at all and the only thing
> we can do is display the page expired page. what exactly is
> "unprofessional" about this.
Well.. this crash :) It is not very 'graceful', maybe better wording
than professionality....
> btw, is your login page https? this may be caused by the fact that you
> will have two different session ids: one secure and one not secure.
This is actually true... however I have a single jetty listening to
:8080 so I would presume it sees a single session.
**
Martin
> On Tue, Jun 16, 2009 at 12:21 PM, Martin
> Makundi<ma...@koodaripalvelut.com> wrote:
>> I have a feeling this has something to do with the littlebit
>> 'unprofessional' way of wicket's dealing with session expiration on
>> stateful pages. Wicket sort of deals with session expiration like if
>> it was a fatal state.. while it is just daily bloody normal ;)
>> Anyways... I will look into this, it's bugged me for 1 year now and I
>> have managed to override it but not solve it.
>>
>> **
>> Martin
>>
>> 2009/6/16 Igor Vaynberg <ig...@gmail.com>:
>>> so the curiosity is why is wicket trying to submit the loginform to
>>> the mainpage? i dont think i have seen anything like this before. if
>>> you can find a way to reproduce it we will be happy to fix it.
>>>
>>> -igor
>>>
>>> On Tue, Jun 16, 2009 at 11:54 AM, Martin
>>> Makundi<ma...@koodaripalvelut.com> wrote:
>>>> No. MainPage is the page the user has probably bookmarked or something.. it
>>>> is the page after successful login.
>>>> **
>>>> Martin
>>>>
>>>> 2009/6/16 Igor Vaynberg <ig...@gmail.com>
>>>>
>>>>> is your LoginPage the com.domain.view.application.MainPage ?
>>>>>
>>>>> -igor
>>>>>
>>>>> On Tue, Jun 16, 2009 at 9:54 AM, Martin
>>>>> Makundi<ma...@koodaripalvelut.com> wrote:
>>>>> > I am not actually sure how to repeat this bug, this is what I see on
>>>>> > the production log.
>>>>> >
>>>>> > **
>>>>> > Martin
>>>>> >
>>>>> > 2009/6/16 Igor Vaynberg <ig...@gmail.com>:
>>>>> >> IFormSubmitListener? so this happens when you submit the login page?
>>>>> >>
>>>>> >> -igor
>>>>> >>
>>>>> >> On Tue, Jun 16, 2009 at 9:30 AM, Martin
>>>>> >> Makundi<ma...@koodaripalvelut.com> wrote:
>>>>> >>>> IIRC, for this purpose I had written a separate expired page but I had
>>>>> >>>> thrown a new restartresponseexception(LoginPage.class) which was
>>>>> working
>>>>> >>>> fine with wicket 1.3.4.
>>>>> >>>
>>>>> >>> So is there a bug with the pageparameters for a stateful page? They
>>>>> >>> should be thrown away when pageExpired occurs (this happens
>>>>> >>> automatically with restartresponseexception?)?
>>>>> >>>
>>>>> >>> Here is some more of the stack:
>>>>> >
>>>>> > ---------------------------------------------------------------------
>>>>> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>> > For additional commands, e-mail: users-help@wicket.apache.org
>>>>> >
>>>>> >
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>>
>>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Login page crashes if old bookmark
Posted by Igor Vaynberg <ig...@gmail.com>.
as far as wicket is concerned it does the best it can. when the
session is gone we have no state information at all and the only thing
we can do is display the page expired page. what exactly is
"unprofessional" about this.
btw, is your login page https? this may be caused by the fact that you
will have two different session ids: one secure and one not secure.
-igor
On Tue, Jun 16, 2009 at 12:21 PM, Martin
Makundi<ma...@koodaripalvelut.com> wrote:
> I have a feeling this has something to do with the littlebit
> 'unprofessional' way of wicket's dealing with session expiration on
> stateful pages. Wicket sort of deals with session expiration like if
> it was a fatal state.. while it is just daily bloody normal ;)
> Anyways... I will look into this, it's bugged me for 1 year now and I
> have managed to override it but not solve it.
>
> **
> Martin
>
> 2009/6/16 Igor Vaynberg <ig...@gmail.com>:
>> so the curiosity is why is wicket trying to submit the loginform to
>> the mainpage? i dont think i have seen anything like this before. if
>> you can find a way to reproduce it we will be happy to fix it.
>>
>> -igor
>>
>> On Tue, Jun 16, 2009 at 11:54 AM, Martin
>> Makundi<ma...@koodaripalvelut.com> wrote:
>>> No. MainPage is the page the user has probably bookmarked or something.. it
>>> is the page after successful login.
>>> **
>>> Martin
>>>
>>> 2009/6/16 Igor Vaynberg <ig...@gmail.com>
>>>
>>>> is your LoginPage the com.domain.view.application.MainPage ?
>>>>
>>>> -igor
>>>>
>>>> On Tue, Jun 16, 2009 at 9:54 AM, Martin
>>>> Makundi<ma...@koodaripalvelut.com> wrote:
>>>> > I am not actually sure how to repeat this bug, this is what I see on
>>>> > the production log.
>>>> >
>>>> > **
>>>> > Martin
>>>> >
>>>> > 2009/6/16 Igor Vaynberg <ig...@gmail.com>:
>>>> >> IFormSubmitListener? so this happens when you submit the login page?
>>>> >>
>>>> >> -igor
>>>> >>
>>>> >> On Tue, Jun 16, 2009 at 9:30 AM, Martin
>>>> >> Makundi<ma...@koodaripalvelut.com> wrote:
>>>> >>>> IIRC, for this purpose I had written a separate expired page but I had
>>>> >>>> thrown a new restartresponseexception(LoginPage.class) which was
>>>> working
>>>> >>>> fine with wicket 1.3.4.
>>>> >>>
>>>> >>> So is there a bug with the pageparameters for a stateful page? They
>>>> >>> should be thrown away when pageExpired occurs (this happens
>>>> >>> automatically with restartresponseexception?)?
>>>> >>>
>>>> >>> Here is some more of the stack:
>>>> >
>>>> > ---------------------------------------------------------------------
>>>> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> > For additional commands, e-mail: users-help@wicket.apache.org
>>>> >
>>>> >
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Login page crashes if old bookmark
Posted by Martin Makundi <ma...@koodaripalvelut.com>.
I have a feeling this has something to do with the littlebit
'unprofessional' way of wicket's dealing with session expiration on
stateful pages. Wicket sort of deals with session expiration like if
it was a fatal state.. while it is just daily bloody normal ;)
Anyways... I will look into this, it's bugged me for 1 year now and I
have managed to override it but not solve it.
**
Martin
2009/6/16 Igor Vaynberg <ig...@gmail.com>:
> so the curiosity is why is wicket trying to submit the loginform to
> the mainpage? i dont think i have seen anything like this before. if
> you can find a way to reproduce it we will be happy to fix it.
>
> -igor
>
> On Tue, Jun 16, 2009 at 11:54 AM, Martin
> Makundi<ma...@koodaripalvelut.com> wrote:
>> No. MainPage is the page the user has probably bookmarked or something.. it
>> is the page after successful login.
>> **
>> Martin
>>
>> 2009/6/16 Igor Vaynberg <ig...@gmail.com>
>>
>>> is your LoginPage the com.domain.view.application.MainPage ?
>>>
>>> -igor
>>>
>>> On Tue, Jun 16, 2009 at 9:54 AM, Martin
>>> Makundi<ma...@koodaripalvelut.com> wrote:
>>> > I am not actually sure how to repeat this bug, this is what I see on
>>> > the production log.
>>> >
>>> > **
>>> > Martin
>>> >
>>> > 2009/6/16 Igor Vaynberg <ig...@gmail.com>:
>>> >> IFormSubmitListener? so this happens when you submit the login page?
>>> >>
>>> >> -igor
>>> >>
>>> >> On Tue, Jun 16, 2009 at 9:30 AM, Martin
>>> >> Makundi<ma...@koodaripalvelut.com> wrote:
>>> >>>> IIRC, for this purpose I had written a separate expired page but I had
>>> >>>> thrown a new restartresponseexception(LoginPage.class) which was
>>> working
>>> >>>> fine with wicket 1.3.4.
>>> >>>
>>> >>> So is there a bug with the pageparameters for a stateful page? They
>>> >>> should be thrown away when pageExpired occurs (this happens
>>> >>> automatically with restartresponseexception?)?
>>> >>>
>>> >>> Here is some more of the stack:
>>> >
>>> > ---------------------------------------------------------------------
>>> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> > For additional commands, e-mail: users-help@wicket.apache.org
>>> >
>>> >
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Login page crashes if old bookmark
Posted by Igor Vaynberg <ig...@gmail.com>.
so the curiosity is why is wicket trying to submit the loginform to
the mainpage? i dont think i have seen anything like this before. if
you can find a way to reproduce it we will be happy to fix it.
-igor
On Tue, Jun 16, 2009 at 11:54 AM, Martin
Makundi<ma...@koodaripalvelut.com> wrote:
> No. MainPage is the page the user has probably bookmarked or something.. it
> is the page after successful login.
> **
> Martin
>
> 2009/6/16 Igor Vaynberg <ig...@gmail.com>
>
>> is your LoginPage the com.domain.view.application.MainPage ?
>>
>> -igor
>>
>> On Tue, Jun 16, 2009 at 9:54 AM, Martin
>> Makundi<ma...@koodaripalvelut.com> wrote:
>> > I am not actually sure how to repeat this bug, this is what I see on
>> > the production log.
>> >
>> > **
>> > Martin
>> >
>> > 2009/6/16 Igor Vaynberg <ig...@gmail.com>:
>> >> IFormSubmitListener? so this happens when you submit the login page?
>> >>
>> >> -igor
>> >>
>> >> On Tue, Jun 16, 2009 at 9:30 AM, Martin
>> >> Makundi<ma...@koodaripalvelut.com> wrote:
>> >>>> IIRC, for this purpose I had written a separate expired page but I had
>> >>>> thrown a new restartresponseexception(LoginPage.class) which was
>> working
>> >>>> fine with wicket 1.3.4.
>> >>>
>> >>> So is there a bug with the pageparameters for a stateful page? They
>> >>> should be thrown away when pageExpired occurs (this happens
>> >>> automatically with restartresponseexception?)?
>> >>>
>> >>> Here is some more of the stack:
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> > For additional commands, e-mail: users-help@wicket.apache.org
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Login page crashes if old bookmark
Posted by Martin Makundi <ma...@koodaripalvelut.com>.
No. MainPage is the page the user has probably bookmarked or something.. it
is the page after successful login.
**
Martin
2009/6/16 Igor Vaynberg <ig...@gmail.com>
> is your LoginPage the com.domain.view.application.MainPage ?
>
> -igor
>
> On Tue, Jun 16, 2009 at 9:54 AM, Martin
> Makundi<ma...@koodaripalvelut.com> wrote:
> > I am not actually sure how to repeat this bug, this is what I see on
> > the production log.
> >
> > **
> > Martin
> >
> > 2009/6/16 Igor Vaynberg <ig...@gmail.com>:
> >> IFormSubmitListener? so this happens when you submit the login page?
> >>
> >> -igor
> >>
> >> On Tue, Jun 16, 2009 at 9:30 AM, Martin
> >> Makundi<ma...@koodaripalvelut.com> wrote:
> >>>> IIRC, for this purpose I had written a separate expired page but I had
> >>>> thrown a new restartresponseexception(LoginPage.class) which was
> working
> >>>> fine with wicket 1.3.4.
> >>>
> >>> So is there a bug with the pageparameters for a stateful page? They
> >>> should be thrown away when pageExpired occurs (this happens
> >>> automatically with restartresponseexception?)?
> >>>
> >>> Here is some more of the stack:
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: Login page crashes if old bookmark
Posted by Igor Vaynberg <ig...@gmail.com>.
is your LoginPage the com.domain.view.application.MainPage ?
-igor
On Tue, Jun 16, 2009 at 9:54 AM, Martin
Makundi<ma...@koodaripalvelut.com> wrote:
> I am not actually sure how to repeat this bug, this is what I see on
> the production log.
>
> **
> Martin
>
> 2009/6/16 Igor Vaynberg <ig...@gmail.com>:
>> IFormSubmitListener? so this happens when you submit the login page?
>>
>> -igor
>>
>> On Tue, Jun 16, 2009 at 9:30 AM, Martin
>> Makundi<ma...@koodaripalvelut.com> wrote:
>>>> IIRC, for this purpose I had written a separate expired page but I had
>>>> thrown a new restartresponseexception(LoginPage.class) which was working
>>>> fine with wicket 1.3.4.
>>>
>>> So is there a bug with the pageparameters for a stateful page? They
>>> should be thrown away when pageExpired occurs (this happens
>>> automatically with restartresponseexception?)?
>>>
>>> Here is some more of the stack:
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Login page crashes if old bookmark
Posted by Martin Makundi <ma...@koodaripalvelut.com>.
I am not actually sure how to repeat this bug, this is what I see on
the production log.
**
Martin
2009/6/16 Igor Vaynberg <ig...@gmail.com>:
> IFormSubmitListener? so this happens when you submit the login page?
>
> -igor
>
> On Tue, Jun 16, 2009 at 9:30 AM, Martin
> Makundi<ma...@koodaripalvelut.com> wrote:
>>> IIRC, for this purpose I had written a separate expired page but I had
>>> thrown a new restartresponseexception(LoginPage.class) which was working
>>> fine with wicket 1.3.4.
>>
>> So is there a bug with the pageparameters for a stateful page? They
>> should be thrown away when pageExpired occurs (this happens
>> automatically with restartresponseexception?)?
>>
>> Here is some more of the stack:
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Login page crashes if old bookmark
Posted by Igor Vaynberg <ig...@gmail.com>.
IFormSubmitListener? so this happens when you submit the login page?
-igor
On Tue, Jun 16, 2009 at 9:30 AM, Martin
Makundi<ma...@koodaripalvelut.com> wrote:
>> IIRC, for this purpose I had written a separate expired page but I had
>> thrown a new restartresponseexception(LoginPage.class) which was working
>> fine with wicket 1.3.4.
>
> So is there a bug with the pageparameters for a stateful page? They
> should be thrown away when pageExpired occurs (this happens
> automatically with restartresponseexception?)?
>
> Here is some more of the stack:
>
> 2009-06-06 21:52:58,998 114074809 [btpool0-212] ERROR RequestCycle -
> component loginForm not found on page
> com.domain.view.application.MainPage[id = 0], listener interface =
> [RequestListenerInterface name=IFormSubmitListener, method=public
> abstract void org.apache.wicket.markup.html.form.IFormSubmitListener.onFormSubmitted()]
> org.apache.wicket.WicketRuntimeException: component loginForm not
> found on page com.domain.view.application.MainPage[id = 0], listener
> interface = [RequestListenerInterface name=IFormSubmitListener,
> method=public abstract void
> org.apache.wicket.markup.html.form.IFormSubmitListener.onFormSubmitted()]
> at org.apache.wicket.request.AbstractRequestCycleProcessor.resolveListenerInterfaceTarget(AbstractRequestCycleProcessor.java:426)
> at org.apache.wicket.request.AbstractRequestCycleProcessor.resolveRenderedPage(AbstractRequestCycleProcessor.java:471)
> at org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequestCycleProcessor.java:139)
> at org.apache.wicket.RequestCycle.step(RequestCycle.java:1300)
> at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1418)
> at org.apache.wicket.RequestCycle.request(RequestCycle.java:544)
> at org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:456)
> at org.apache.wicket.protocol.http.WicketServlet.doPost(WicketServlet.java:160)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
> at wicket.quickstart.TakpServlet.service(TakpServlet.java:48)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
> at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:491)
> at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:367)
> at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:185)
> at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
> at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:689)
> at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:391)
> at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:146)
> at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
> at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
> at org.mortbay.jetty.Server.handle(Server.java:285)
> at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:457)
> at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:765)
> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:627)
> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:209)
> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:357)
> at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:329)
> at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475)
>
> **
> Martin
>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Login page crashes if old bookmark
Posted by Martin Makundi <ma...@koodaripalvelut.com>.
> IIRC, for this purpose I had written a separate expired page but I had
> thrown a new restartresponseexception(LoginPage.class) which was working
> fine with wicket 1.3.4.
So is there a bug with the pageparameters for a stateful page? They
should be thrown away when pageExpired occurs (this happens
automatically with restartresponseexception?)?
Here is some more of the stack:
2009-06-06 21:52:58,998 114074809 [btpool0-212] ERROR RequestCycle -
component loginForm not found on page
com.domain.view.application.MainPage[id = 0], listener interface =
[RequestListenerInterface name=IFormSubmitListener, method=public
abstract void org.apache.wicket.markup.html.form.IFormSubmitListener.onFormSubmitted()]
org.apache.wicket.WicketRuntimeException: component loginForm not
found on page com.domain.view.application.MainPage[id = 0], listener
interface = [RequestListenerInterface name=IFormSubmitListener,
method=public abstract void
org.apache.wicket.markup.html.form.IFormSubmitListener.onFormSubmitted()]
at org.apache.wicket.request.AbstractRequestCycleProcessor.resolveListenerInterfaceTarget(AbstractRequestCycleProcessor.java:426)
at org.apache.wicket.request.AbstractRequestCycleProcessor.resolveRenderedPage(AbstractRequestCycleProcessor.java:471)
at org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequestCycleProcessor.java:139)
at org.apache.wicket.RequestCycle.step(RequestCycle.java:1300)
at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1418)
at org.apache.wicket.RequestCycle.request(RequestCycle.java:544)
at org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:456)
at org.apache.wicket.protocol.http.WicketServlet.doPost(WicketServlet.java:160)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at wicket.quickstart.TakpServlet.service(TakpServlet.java:48)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:491)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:367)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:185)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:689)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:391)
at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:146)
at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java:285)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:457)
at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:765)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:627)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:209)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:357)
at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:329)
at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475)
**
Martin
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: 1.4 trunk broken?
Posted by James Carman <jc...@carmanconsulting.com>.
Yeah, we could, but then I'd have to make up a new version number for
it, since the release plugin doesn't allow SNAPSHOT dependencies. If
you guys are going to have rc7 out the door soon, I can just wait.
The rc4 release works just fine.
On Wed, Jul 8, 2009 at 11:38 AM, Igor Vaynberg<ig...@gmail.com> wrote:
> you can always build your own jar from trunk
>
> -igor
>
> On Wed, Jul 8, 2009 at 4:43 AM, James
> Carman<jc...@carmanconsulting.com> wrote:
>> Yeah, there was a message that just sent out about it. It's
>> WICKET-2346. When can we expect a new release? This is a nasty bug
>> in our production environment (yes, I know I shouldn't be using an rc
>> in production, but we didn't want to have to change the code to
>> genericize it after an "official" 1.4 release). For now, we're going
>> to back out to 1.4-rc4.
>>
>>
>> On Wed, Jul 8, 2009 at 7:34 AM, Johan Compagner<jc...@gmail.com> wrote:
>>> i think in trunk it should be fixed.
>>>
>>> On Wed, Jul 8, 2009 at 13:20, James Carman <jc...@carmanconsulting.com>wrote:
>>>
>>>> Have we fixed this? I'm getting the same error.
>>>>
>>>> On Wed, Jun 17, 2009 at 3:00 PM, Stefan Lindner<li...@visionet.de>
>>>> wrote:
>>>> > The problem occurs when I klicked around on a page an then deploy a new
>>>> version of the app.
>>>> > When I klick on a page link now then the error occurs. In former trunk
>>>> versions and all former wicket version I was redirected to the application's
>>>> homepage.
>>>> >
>>>> > Stefan
>>>> >
>>>> > -----Ursprüngliche Nachricht-----
>>>> > Von: Johan Compagner [mailto:jcompagner@gmail.com]
>>>> > Gesendet: Dienstag, 16. Juni 2009 20:19
>>>> > An: users@wicket.apache.org
>>>> > Betreff: Re: 1.4 trunk broken?
>>>> >
>>>> > i do remember one change for that invalidurlexception
>>>> > (that we should throw that as an exception instead of just a page expired
>>>> or
>>>> > something)
>>>> >
>>>> > On Tue, Jun 16, 2009 at 18:09, Stefan Lindner <li...@visionet.de>
>>>> wrote:
>>>> >
>>>> >> Using current 1.4 trunk gives me the error
>>>> >>
>>>> >> [RequestCycle] org.apache.wicket.protocol.http.PageExpiredException:
>>>> >> Cannot find the rendered page in session [pagemap=nu
>>>> >> ll,componentPath=1,versionNumber=0]
>>>> >> org.apache.wicket.protocol.http.request.InvalidUrlException:
>>>> >> org.apache.wicket.protocol.http.PageExpiredException: Cannot find the
>>>> >> rendered
>>>> >> page in session [pagemap=null,componentPath=1,versionNumber=0]
>>>> >> at
>>>> >> org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequ
>>>> >> estCycleProcessor.java:250)
>>>> >> at org.apache.wicket.RequestCycle.step(RequestCycle.java:1301)
>>>> >> at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1419)
>>>> >> at org.apache.wicket.RequestCycle.request(RequestCycle.java:545)
>>>> >> at
>>>> >> org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:456
>>>> >> )
>>>> >> at
>>>> >> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:
>>>> >> 289)
>>>> >> at
>>>> >> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
>>>> >> tionFilterChain.java:235)
>>>> >> at
>>>> >> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
>>>> >> erChain.java:206)
>>>> >> at
>>>> >> org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilte
>>>> >> r.java:96)
>>>> >> at
>>>> >> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
>>>> >> tionFilterChain.java:235)
>>>> >> at
>>>> >> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
>>>> >> erChain.java:206)
>>>> >> at
>>>> >> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv
>>>> >> e.java:235)
>>>> >> at
>>>> >> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv
>>>> >> e.java:191)
>>>> >> at
>>>> >> org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAs
>>>> >> sociationValve.java:190)
>>>> >> at
>>>> >> org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.j
>>>> >> ava:92)
>>>> >> at
>>>> >> org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(
>>>> >> SecurityContextEstablishmentValve.java:126)
>>>> >> at
>>>> >> org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(S
>>>> >> ecurityContextEstablishmentValve.java:70)
>>>> >> at
>>>> >> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
>>>> >> :127)
>>>> >> at
>>>> >> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
>>>> >> :102)
>>>> >> at
>>>> >> org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConn
>>>> >> ectionValve.java:158)
>>>> >> at
>>>> >> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.
>>>> >> java:109)
>>>> >> at
>>>> >> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:3
>>>> >> 30)
>>>> >> at
>>>> >> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:82
>>>> >> 9)
>>>> >> at
>>>> >> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(
>>>> >> Http11Protocol.java:598)
>>>> >> at
>>>> >> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
>>>> >> at java.lang.Thread.run(Thread.java:619)
>>>> >> Caused by: org.apache.wicket.protocol.http.PageExpiredException: Cannot
>>>> >> find the rendered page in session [pagemap=null,componentPath=1,vers
>>>> >> ionNumber=0]
>>>> >> at
>>>> >> org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequ
>>>> >> estCycleProcessor.java:197)
>>>> >> ... 25 more
>>>> >>
>>>> >>
>>>> >> On loading a page. Did I miss some big change?
>>>> >>
>>>> >> ---------------------------------------------------------------------
>>>> >> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> >> For additional commands, e-mail: users-help@wicket.apache.org
>>>> >>
>>>> >>
>>>> >
>>>> > ---------------------------------------------------------------------
>>>> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> > For additional commands, e-mail: users-help@wicket.apache.org
>>>> >
>>>> >
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>>
>>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: 1.4 trunk broken?
Posted by Igor Vaynberg <ig...@gmail.com>.
you can always build your own jar from trunk
-igor
On Wed, Jul 8, 2009 at 4:43 AM, James
Carman<jc...@carmanconsulting.com> wrote:
> Yeah, there was a message that just sent out about it. It's
> WICKET-2346. When can we expect a new release? This is a nasty bug
> in our production environment (yes, I know I shouldn't be using an rc
> in production, but we didn't want to have to change the code to
> genericize it after an "official" 1.4 release). For now, we're going
> to back out to 1.4-rc4.
>
>
> On Wed, Jul 8, 2009 at 7:34 AM, Johan Compagner<jc...@gmail.com> wrote:
>> i think in trunk it should be fixed.
>>
>> On Wed, Jul 8, 2009 at 13:20, James Carman <jc...@carmanconsulting.com>wrote:
>>
>>> Have we fixed this? I'm getting the same error.
>>>
>>> On Wed, Jun 17, 2009 at 3:00 PM, Stefan Lindner<li...@visionet.de>
>>> wrote:
>>> > The problem occurs when I klicked around on a page an then deploy a new
>>> version of the app.
>>> > When I klick on a page link now then the error occurs. In former trunk
>>> versions and all former wicket version I was redirected to the application's
>>> homepage.
>>> >
>>> > Stefan
>>> >
>>> > -----Ursprüngliche Nachricht-----
>>> > Von: Johan Compagner [mailto:jcompagner@gmail.com]
>>> > Gesendet: Dienstag, 16. Juni 2009 20:19
>>> > An: users@wicket.apache.org
>>> > Betreff: Re: 1.4 trunk broken?
>>> >
>>> > i do remember one change for that invalidurlexception
>>> > (that we should throw that as an exception instead of just a page expired
>>> or
>>> > something)
>>> >
>>> > On Tue, Jun 16, 2009 at 18:09, Stefan Lindner <li...@visionet.de>
>>> wrote:
>>> >
>>> >> Using current 1.4 trunk gives me the error
>>> >>
>>> >> [RequestCycle] org.apache.wicket.protocol.http.PageExpiredException:
>>> >> Cannot find the rendered page in session [pagemap=nu
>>> >> ll,componentPath=1,versionNumber=0]
>>> >> org.apache.wicket.protocol.http.request.InvalidUrlException:
>>> >> org.apache.wicket.protocol.http.PageExpiredException: Cannot find the
>>> >> rendered
>>> >> page in session [pagemap=null,componentPath=1,versionNumber=0]
>>> >> at
>>> >> org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequ
>>> >> estCycleProcessor.java:250)
>>> >> at org.apache.wicket.RequestCycle.step(RequestCycle.java:1301)
>>> >> at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1419)
>>> >> at org.apache.wicket.RequestCycle.request(RequestCycle.java:545)
>>> >> at
>>> >> org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:456
>>> >> )
>>> >> at
>>> >> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:
>>> >> 289)
>>> >> at
>>> >> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
>>> >> tionFilterChain.java:235)
>>> >> at
>>> >> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
>>> >> erChain.java:206)
>>> >> at
>>> >> org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilte
>>> >> r.java:96)
>>> >> at
>>> >> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
>>> >> tionFilterChain.java:235)
>>> >> at
>>> >> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
>>> >> erChain.java:206)
>>> >> at
>>> >> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv
>>> >> e.java:235)
>>> >> at
>>> >> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv
>>> >> e.java:191)
>>> >> at
>>> >> org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAs
>>> >> sociationValve.java:190)
>>> >> at
>>> >> org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.j
>>> >> ava:92)
>>> >> at
>>> >> org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(
>>> >> SecurityContextEstablishmentValve.java:126)
>>> >> at
>>> >> org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(S
>>> >> ecurityContextEstablishmentValve.java:70)
>>> >> at
>>> >> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
>>> >> :127)
>>> >> at
>>> >> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
>>> >> :102)
>>> >> at
>>> >> org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConn
>>> >> ectionValve.java:158)
>>> >> at
>>> >> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.
>>> >> java:109)
>>> >> at
>>> >> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:3
>>> >> 30)
>>> >> at
>>> >> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:82
>>> >> 9)
>>> >> at
>>> >> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(
>>> >> Http11Protocol.java:598)
>>> >> at
>>> >> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
>>> >> at java.lang.Thread.run(Thread.java:619)
>>> >> Caused by: org.apache.wicket.protocol.http.PageExpiredException: Cannot
>>> >> find the rendered page in session [pagemap=null,componentPath=1,vers
>>> >> ionNumber=0]
>>> >> at
>>> >> org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequ
>>> >> estCycleProcessor.java:197)
>>> >> ... 25 more
>>> >>
>>> >>
>>> >> On loading a page. Did I miss some big change?
>>> >>
>>> >> ---------------------------------------------------------------------
>>> >> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> >> For additional commands, e-mail: users-help@wicket.apache.org
>>> >>
>>> >>
>>> >
>>> > ---------------------------------------------------------------------
>>> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> > For additional commands, e-mail: users-help@wicket.apache.org
>>> >
>>> >
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: 1.4 trunk broken?
Posted by James Carman <jc...@carmanconsulting.com>.
Yeah, there was a message that just sent out about it. It's
WICKET-2346. When can we expect a new release? This is a nasty bug
in our production environment (yes, I know I shouldn't be using an rc
in production, but we didn't want to have to change the code to
genericize it after an "official" 1.4 release). For now, we're going
to back out to 1.4-rc4.
On Wed, Jul 8, 2009 at 7:34 AM, Johan Compagner<jc...@gmail.com> wrote:
> i think in trunk it should be fixed.
>
> On Wed, Jul 8, 2009 at 13:20, James Carman <jc...@carmanconsulting.com>wrote:
>
>> Have we fixed this? I'm getting the same error.
>>
>> On Wed, Jun 17, 2009 at 3:00 PM, Stefan Lindner<li...@visionet.de>
>> wrote:
>> > The problem occurs when I klicked around on a page an then deploy a new
>> version of the app.
>> > When I klick on a page link now then the error occurs. In former trunk
>> versions and all former wicket version I was redirected to the application's
>> homepage.
>> >
>> > Stefan
>> >
>> > -----Ursprüngliche Nachricht-----
>> > Von: Johan Compagner [mailto:jcompagner@gmail.com]
>> > Gesendet: Dienstag, 16. Juni 2009 20:19
>> > An: users@wicket.apache.org
>> > Betreff: Re: 1.4 trunk broken?
>> >
>> > i do remember one change for that invalidurlexception
>> > (that we should throw that as an exception instead of just a page expired
>> or
>> > something)
>> >
>> > On Tue, Jun 16, 2009 at 18:09, Stefan Lindner <li...@visionet.de>
>> wrote:
>> >
>> >> Using current 1.4 trunk gives me the error
>> >>
>> >> [RequestCycle] org.apache.wicket.protocol.http.PageExpiredException:
>> >> Cannot find the rendered page in session [pagemap=nu
>> >> ll,componentPath=1,versionNumber=0]
>> >> org.apache.wicket.protocol.http.request.InvalidUrlException:
>> >> org.apache.wicket.protocol.http.PageExpiredException: Cannot find the
>> >> rendered
>> >> page in session [pagemap=null,componentPath=1,versionNumber=0]
>> >> at
>> >> org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequ
>> >> estCycleProcessor.java:250)
>> >> at org.apache.wicket.RequestCycle.step(RequestCycle.java:1301)
>> >> at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1419)
>> >> at org.apache.wicket.RequestCycle.request(RequestCycle.java:545)
>> >> at
>> >> org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:456
>> >> )
>> >> at
>> >> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:
>> >> 289)
>> >> at
>> >> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
>> >> tionFilterChain.java:235)
>> >> at
>> >> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
>> >> erChain.java:206)
>> >> at
>> >> org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilte
>> >> r.java:96)
>> >> at
>> >> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
>> >> tionFilterChain.java:235)
>> >> at
>> >> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
>> >> erChain.java:206)
>> >> at
>> >> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv
>> >> e.java:235)
>> >> at
>> >> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv
>> >> e.java:191)
>> >> at
>> >> org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAs
>> >> sociationValve.java:190)
>> >> at
>> >> org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.j
>> >> ava:92)
>> >> at
>> >> org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(
>> >> SecurityContextEstablishmentValve.java:126)
>> >> at
>> >> org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(S
>> >> ecurityContextEstablishmentValve.java:70)
>> >> at
>> >> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
>> >> :127)
>> >> at
>> >> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
>> >> :102)
>> >> at
>> >> org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConn
>> >> ectionValve.java:158)
>> >> at
>> >> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.
>> >> java:109)
>> >> at
>> >> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:3
>> >> 30)
>> >> at
>> >> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:82
>> >> 9)
>> >> at
>> >> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(
>> >> Http11Protocol.java:598)
>> >> at
>> >> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
>> >> at java.lang.Thread.run(Thread.java:619)
>> >> Caused by: org.apache.wicket.protocol.http.PageExpiredException: Cannot
>> >> find the rendered page in session [pagemap=null,componentPath=1,vers
>> >> ionNumber=0]
>> >> at
>> >> org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequ
>> >> estCycleProcessor.java:197)
>> >> ... 25 more
>> >>
>> >>
>> >> On loading a page. Did I miss some big change?
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> >> For additional commands, e-mail: users-help@wicket.apache.org
>> >>
>> >>
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> > For additional commands, e-mail: users-help@wicket.apache.org
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: 1.4 trunk broken?
Posted by Johan Compagner <jc...@gmail.com>.
i think in trunk it should be fixed.
On Wed, Jul 8, 2009 at 13:20, James Carman <jc...@carmanconsulting.com>wrote:
> Have we fixed this? I'm getting the same error.
>
> On Wed, Jun 17, 2009 at 3:00 PM, Stefan Lindner<li...@visionet.de>
> wrote:
> > The problem occurs when I klicked around on a page an then deploy a new
> version of the app.
> > When I klick on a page link now then the error occurs. In former trunk
> versions and all former wicket version I was redirected to the application's
> homepage.
> >
> > Stefan
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Johan Compagner [mailto:jcompagner@gmail.com]
> > Gesendet: Dienstag, 16. Juni 2009 20:19
> > An: users@wicket.apache.org
> > Betreff: Re: 1.4 trunk broken?
> >
> > i do remember one change for that invalidurlexception
> > (that we should throw that as an exception instead of just a page expired
> or
> > something)
> >
> > On Tue, Jun 16, 2009 at 18:09, Stefan Lindner <li...@visionet.de>
> wrote:
> >
> >> Using current 1.4 trunk gives me the error
> >>
> >> [RequestCycle] org.apache.wicket.protocol.http.PageExpiredException:
> >> Cannot find the rendered page in session [pagemap=nu
> >> ll,componentPath=1,versionNumber=0]
> >> org.apache.wicket.protocol.http.request.InvalidUrlException:
> >> org.apache.wicket.protocol.http.PageExpiredException: Cannot find the
> >> rendered
> >> page in session [pagemap=null,componentPath=1,versionNumber=0]
> >> at
> >> org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequ
> >> estCycleProcessor.java:250)
> >> at org.apache.wicket.RequestCycle.step(RequestCycle.java:1301)
> >> at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1419)
> >> at org.apache.wicket.RequestCycle.request(RequestCycle.java:545)
> >> at
> >> org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:456
> >> )
> >> at
> >> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:
> >> 289)
> >> at
> >> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
> >> tionFilterChain.java:235)
> >> at
> >> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
> >> erChain.java:206)
> >> at
> >> org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilte
> >> r.java:96)
> >> at
> >> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
> >> tionFilterChain.java:235)
> >> at
> >> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
> >> erChain.java:206)
> >> at
> >> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv
> >> e.java:235)
> >> at
> >> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv
> >> e.java:191)
> >> at
> >> org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAs
> >> sociationValve.java:190)
> >> at
> >> org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.j
> >> ava:92)
> >> at
> >> org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(
> >> SecurityContextEstablishmentValve.java:126)
> >> at
> >> org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(S
> >> ecurityContextEstablishmentValve.java:70)
> >> at
> >> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
> >> :127)
> >> at
> >> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
> >> :102)
> >> at
> >> org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConn
> >> ectionValve.java:158)
> >> at
> >> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.
> >> java:109)
> >> at
> >> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:3
> >> 30)
> >> at
> >> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:82
> >> 9)
> >> at
> >> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(
> >> Http11Protocol.java:598)
> >> at
> >> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
> >> at java.lang.Thread.run(Thread.java:619)
> >> Caused by: org.apache.wicket.protocol.http.PageExpiredException: Cannot
> >> find the rendered page in session [pagemap=null,componentPath=1,vers
> >> ionNumber=0]
> >> at
> >> org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequ
> >> estCycleProcessor.java:197)
> >> ... 25 more
> >>
> >>
> >> On loading a page. Did I miss some big change?
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >> For additional commands, e-mail: users-help@wicket.apache.org
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: 1.4 trunk broken?
Posted by James Carman <jc...@carmanconsulting.com>.
Have we fixed this? I'm getting the same error.
On Wed, Jun 17, 2009 at 3:00 PM, Stefan Lindner<li...@visionet.de> wrote:
> The problem occurs when I klicked around on a page an then deploy a new version of the app.
> When I klick on a page link now then the error occurs. In former trunk versions and all former wicket version I was redirected to the application's homepage.
>
> Stefan
>
> -----Ursprüngliche Nachricht-----
> Von: Johan Compagner [mailto:jcompagner@gmail.com]
> Gesendet: Dienstag, 16. Juni 2009 20:19
> An: users@wicket.apache.org
> Betreff: Re: 1.4 trunk broken?
>
> i do remember one change for that invalidurlexception
> (that we should throw that as an exception instead of just a page expired or
> something)
>
> On Tue, Jun 16, 2009 at 18:09, Stefan Lindner <li...@visionet.de> wrote:
>
>> Using current 1.4 trunk gives me the error
>>
>> [RequestCycle] org.apache.wicket.protocol.http.PageExpiredException:
>> Cannot find the rendered page in session [pagemap=nu
>> ll,componentPath=1,versionNumber=0]
>> org.apache.wicket.protocol.http.request.InvalidUrlException:
>> org.apache.wicket.protocol.http.PageExpiredException: Cannot find the
>> rendered
>> page in session [pagemap=null,componentPath=1,versionNumber=0]
>> at
>> org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequ
>> estCycleProcessor.java:250)
>> at org.apache.wicket.RequestCycle.step(RequestCycle.java:1301)
>> at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1419)
>> at org.apache.wicket.RequestCycle.request(RequestCycle.java:545)
>> at
>> org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:456
>> )
>> at
>> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:
>> 289)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
>> tionFilterChain.java:235)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
>> erChain.java:206)
>> at
>> org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilte
>> r.java:96)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
>> tionFilterChain.java:235)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
>> erChain.java:206)
>> at
>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv
>> e.java:235)
>> at
>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv
>> e.java:191)
>> at
>> org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAs
>> sociationValve.java:190)
>> at
>> org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.j
>> ava:92)
>> at
>> org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(
>> SecurityContextEstablishmentValve.java:126)
>> at
>> org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(S
>> ecurityContextEstablishmentValve.java:70)
>> at
>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
>> :127)
>> at
>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
>> :102)
>> at
>> org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConn
>> ectionValve.java:158)
>> at
>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.
>> java:109)
>> at
>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:3
>> 30)
>> at
>> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:82
>> 9)
>> at
>> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(
>> Http11Protocol.java:598)
>> at
>> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
>> at java.lang.Thread.run(Thread.java:619)
>> Caused by: org.apache.wicket.protocol.http.PageExpiredException: Cannot
>> find the rendered page in session [pagemap=null,componentPath=1,vers
>> ionNumber=0]
>> at
>> org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequ
>> estCycleProcessor.java:197)
>> ... 25 more
>>
>>
>> On loading a page. Did I miss some big change?
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
RE: 1.4 trunk broken?
Posted by Stefan Lindner <li...@visionet.de>.
The problem occurs when I klicked around on a page an then deploy a new version of the app.
When I klick on a page link now then the error occurs. In former trunk versions and all former wicket version I was redirected to the application's homepage.
Stefan
-----Ursprüngliche Nachricht-----
Von: Johan Compagner [mailto:jcompagner@gmail.com]
Gesendet: Dienstag, 16. Juni 2009 20:19
An: users@wicket.apache.org
Betreff: Re: 1.4 trunk broken?
i do remember one change for that invalidurlexception
(that we should throw that as an exception instead of just a page expired or
something)
On Tue, Jun 16, 2009 at 18:09, Stefan Lindner <li...@visionet.de> wrote:
> Using current 1.4 trunk gives me the error
>
> [RequestCycle] org.apache.wicket.protocol.http.PageExpiredException:
> Cannot find the rendered page in session [pagemap=nu
> ll,componentPath=1,versionNumber=0]
> org.apache.wicket.protocol.http.request.InvalidUrlException:
> org.apache.wicket.protocol.http.PageExpiredException: Cannot find the
> rendered
> page in session [pagemap=null,componentPath=1,versionNumber=0]
> at
> org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequ
> estCycleProcessor.java:250)
> at org.apache.wicket.RequestCycle.step(RequestCycle.java:1301)
> at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1419)
> at org.apache.wicket.RequestCycle.request(RequestCycle.java:545)
> at
> org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:456
> )
> at
> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:
> 289)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
> tionFilterChain.java:235)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
> erChain.java:206)
> at
> org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilte
> r.java:96)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
> tionFilterChain.java:235)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
> erChain.java:206)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv
> e.java:235)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv
> e.java:191)
> at
> org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAs
> sociationValve.java:190)
> at
> org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.j
> ava:92)
> at
> org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(
> SecurityContextEstablishmentValve.java:126)
> at
> org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(S
> ecurityContextEstablishmentValve.java:70)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
> :127)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
> :102)
> at
> org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConn
> ectionValve.java:158)
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.
> java:109)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:3
> 30)
> at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:82
> 9)
> at
> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(
> Http11Protocol.java:598)
> at
> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
> at java.lang.Thread.run(Thread.java:619)
> Caused by: org.apache.wicket.protocol.http.PageExpiredException: Cannot
> find the rendered page in session [pagemap=null,componentPath=1,vers
> ionNumber=0]
> at
> org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequ
> estCycleProcessor.java:197)
> ... 25 more
>
>
> On loading a page. Did I miss some big change?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: 1.4 trunk broken?
Posted by Johan Compagner <jc...@gmail.com>.
i do remember one change for that invalidurlexception
(that we should throw that as an exception instead of just a page expired or
something)
On Tue, Jun 16, 2009 at 18:09, Stefan Lindner <li...@visionet.de> wrote:
> Using current 1.4 trunk gives me the error
>
> [RequestCycle] org.apache.wicket.protocol.http.PageExpiredException:
> Cannot find the rendered page in session [pagemap=nu
> ll,componentPath=1,versionNumber=0]
> org.apache.wicket.protocol.http.request.InvalidUrlException:
> org.apache.wicket.protocol.http.PageExpiredException: Cannot find the
> rendered
> page in session [pagemap=null,componentPath=1,versionNumber=0]
> at
> org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequ
> estCycleProcessor.java:250)
> at org.apache.wicket.RequestCycle.step(RequestCycle.java:1301)
> at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1419)
> at org.apache.wicket.RequestCycle.request(RequestCycle.java:545)
> at
> org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:456
> )
> at
> org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:
> 289)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
> tionFilterChain.java:235)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
> erChain.java:206)
> at
> org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilte
> r.java:96)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
> tionFilterChain.java:235)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
> erChain.java:206)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv
> e.java:235)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv
> e.java:191)
> at
> org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAs
> sociationValve.java:190)
> at
> org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.j
> ava:92)
> at
> org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(
> SecurityContextEstablishmentValve.java:126)
> at
> org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(S
> ecurityContextEstablishmentValve.java:70)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
> :127)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
> :102)
> at
> org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConn
> ectionValve.java:158)
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.
> java:109)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:3
> 30)
> at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:82
> 9)
> at
> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(
> Http11Protocol.java:598)
> at
> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
> at java.lang.Thread.run(Thread.java:619)
> Caused by: org.apache.wicket.protocol.http.PageExpiredException: Cannot
> find the rendered page in session [pagemap=null,componentPath=1,vers
> ionNumber=0]
> at
> org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequ
> estCycleProcessor.java:197)
> ... 25 more
>
>
> On loading a page. Did I miss some big change?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
1.4 trunk broken?
Posted by Stefan Lindner <li...@visionet.de>.
Using current 1.4 trunk gives me the error
[RequestCycle] org.apache.wicket.protocol.http.PageExpiredException:
Cannot find the rendered page in session [pagemap=nu
ll,componentPath=1,versionNumber=0]
org.apache.wicket.protocol.http.request.InvalidUrlException:
org.apache.wicket.protocol.http.PageExpiredException: Cannot find the
rendered
page in session [pagemap=null,componentPath=1,versionNumber=0]
at
org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequ
estCycleProcessor.java:250)
at org.apache.wicket.RequestCycle.step(RequestCycle.java:1301)
at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1419)
at org.apache.wicket.RequestCycle.request(RequestCycle.java:545)
at
org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:456
)
at
org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:
289)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:206)
at
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilte
r.java:96)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica
tionFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt
erChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv
e.java:235)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv
e.java:191)
at
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAs
sociationValve.java:190)
at
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.j
ava:92)
at
org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(
SecurityContextEstablishmentValve.java:126)
at
org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(S
ecurityContextEstablishmentValve.java:70)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java
:127)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java
:102)
at
org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConn
ectionValve.java:158)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.
java:109)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:3
30)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:82
9)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(
Http11Protocol.java:598)
at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.apache.wicket.protocol.http.PageExpiredException: Cannot
find the rendered page in session [pagemap=null,componentPath=1,vers
ionNumber=0]
at
org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequ
estCycleProcessor.java:197)
... 25 more
On loading a page. Did I miss some big change?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Login page crashes if old bookmark
Posted by Serkan Camurcuoglu <Se...@telenity.com>.
IIRC, for this purpose I had written a separate expired page but I had
thrown a new restartresponseexception(LoginPage.class) which was working
fine with wicket 1.3.4.
Martin Makundi wrote:
>> the users should get a page expired error if they come in from a
>> stateful bookmark and the session is expired.
>>
>
> Well.. in order to avoid that I have attempted to redirect them onto
> the login page by setting the LoginPage to be the expired page ;)
>
> getApplicationSettings().setPageExpiredErrorPage(LoginPage.class);
>
> I do not want a separate "pageExpiredErrorPage" to be displayed to the
> user, just go back to login with no error messages. Now I get the
> component loginForm not found on page... I would assume that
> LoginPage.class is a clean initiation with no pageParameters.
>
> **
> Martin
>
>
>> On Tue, Jun 16, 2009 at 12:58 AM, Martin
>> Makundi<ma...@koodaripalvelut.com> wrote:
>>
>>> Hi!
>>>
>>> I get the following error when users come to the login page using a
>>> stateful bookmark:
>>> 2009-06-16 10:11:52,861 43237745 [btpool0-115] ERROR RequestCycle -
>>> component loginForm not found on page
>>>
>>> Any tricks how this can be avoided?
>>>
>>> **
>>> Martin
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Login page crashes if old bookmark
Posted by Igor Vaynberg <ig...@gmail.com>.
show more of the stacktrace
-igor
On Tue, Jun 16, 2009 at 8:35 AM, Martin
Makundi<ma...@koodaripalvelut.com> wrote:
>> the users should get a page expired error if they come in from a
>> stateful bookmark and the session is expired.
>
> Well.. in order to avoid that I have attempted to redirect them onto
> the login page by setting the LoginPage to be the expired page ;)
>
> getApplicationSettings().setPageExpiredErrorPage(LoginPage.class);
>
> I do not want a separate "pageExpiredErrorPage" to be displayed to the
> user, just go back to login with no error messages. Now I get the
> component loginForm not found on page... I would assume that
> LoginPage.class is a clean initiation with no pageParameters.
>
> **
> Martin
>
>>
>> On Tue, Jun 16, 2009 at 12:58 AM, Martin
>> Makundi<ma...@koodaripalvelut.com> wrote:
>>> Hi!
>>>
>>> I get the following error when users come to the login page using a
>>> stateful bookmark:
>>> 2009-06-16 10:11:52,861 43237745 [btpool0-115] ERROR RequestCycle -
>>> component loginForm not found on page
>>>
>>> Any tricks how this can be avoided?
>>>
>>> **
>>> Martin
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>>> For additional commands, e-mail: users-help@wicket.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Login page crashes if old bookmark
Posted by Martin Makundi <ma...@koodaripalvelut.com>.
> the users should get a page expired error if they come in from a
> stateful bookmark and the session is expired.
Well.. in order to avoid that I have attempted to redirect them onto
the login page by setting the LoginPage to be the expired page ;)
getApplicationSettings().setPageExpiredErrorPage(LoginPage.class);
I do not want a separate "pageExpiredErrorPage" to be displayed to the
user, just go back to login with no error messages. Now I get the
component loginForm not found on page... I would assume that
LoginPage.class is a clean initiation with no pageParameters.
**
Martin
>
> On Tue, Jun 16, 2009 at 12:58 AM, Martin
> Makundi<ma...@koodaripalvelut.com> wrote:
>> Hi!
>>
>> I get the following error when users come to the login page using a
>> stateful bookmark:
>> 2009-06-16 10:11:52,861 43237745 [btpool0-115] ERROR RequestCycle -
>> component loginForm not found on page
>>
>> Any tricks how this can be avoided?
>>
>> **
>> Martin
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Login page crashes if old bookmark
Posted by Igor Vaynberg <ig...@gmail.com>.
the users should get a page expired error if they come in from a
stateful bookmark and the session is expired.
-igor
On Tue, Jun 16, 2009 at 12:58 AM, Martin
Makundi<ma...@koodaripalvelut.com> wrote:
> Hi!
>
> I get the following error when users come to the login page using a
> stateful bookmark:
> 2009-06-16 10:11:52,861 43237745 [btpool0-115] ERROR RequestCycle -
> component loginForm not found on page
>
> Any tricks how this can be avoided?
>
> **
> Martin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org