IE7 + ajax + cookie = no go?

[Istvan Soos]

Hi,

I've a page where the user can edit his/her settings through an
ajax-updated form. Each time a setting is modified it is being sent to
the server side, stored in the session and in the database, and I
issue a new cookie that contains the value too. (Of course if the user
is not authenticated, only the session and the cookie is updated). Now
the symptom is that IE7 keeps forgetting the cookie (and/or the
session?). Does anybody else encountered similar problem? What could
be the solution?

Regards,
  Istvan

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Wicketstuff updated!

[Jeremy Thomerson]

there's already an attic - why create a new one?  it will just generate more
emails to the list whining about "i can't find such and such" - by those who
can't use the search function well.  there's nothing special about an
ex-core project that means it needs its own attic

--
Jeremy Thomerson
http://www.wickettraining.com



On Wed, Mar 31, 2010 at 11:57 AM, nino martinez wael <
nino.martinez.w...@gmail.com> wrote:

> I guess we could start a branch, called wicketstuff-core-attic. Then
> upgrade them to latest wicket version and see if they work and if not,
> then remove them. Unless someone wants to fix the errors.
>
> 2010/3/28 Major Péter :
> > JavaEE-Inject is tested, and OK.
> >
> > It looks like there are projects, which are depending to a specific
> > wicket version (1.4-rc*, 1.4.5):
> > * multi-text-input-parent
> > * flot-parent/flot
> > * flot-parent/flot-examples
> > * wicket-html5-parent
> > * ddcalendar-parent/ddcalendar
> > * ddcalendar-parent/ddcalendar-examples
> >
> > What's going to happen with them?
> >
> > Regards,
> > Peter
> >
> > 2010-03-24 22:14 keltezéssel, Boris Goldowsky írta:
> >> As discussed, and not hearing any objections, I've updated the
> >> wicketstuff-core project to depend on Wicket 1.4.7.  wicketstuff-core's
> >> version number is now 1.4.7-SNAPSHOT, and the idea is that people can
> >> test it, and barring any major problems it can be released as a stable
> >> version 1.4.7 .
> >>
> >> Now, before people can easily test this, the artifacts need to get into
> >> the wicket snapshots maven repository, right?  Can someone with the
> >> requisite permissions make this happen?  In the meantime of course
> >> people are encouraged to download the projects and build and test them
> >> locally.
> >>
> >> In addition to wicket, the following dependencies were also updated to
> >> the latest stable version within the same major version of the project.
> >> I did not attempt to move Lucene from version 2.4.1 to 3.0.1, for
> >> instance, since more significant changes might be required for this (if
> >> any subproject is actually using it).
> >>
> >>  Jetty: 6.1.22
> >>  Lucene: 2.4.1
> >>  slf4j: 1.5.11
> >>  JUnit: 4.8.1
> >>
> >> I had to make a couple of changes to get everything to build with the
> >> new dependencies (commented out wagon-ssh-external extension from
> >> inmethod-grid; added new required constructor argument to two instances
> >> of SpringComponentInjector).  People should test the build and make sure
> >> these changes are ok.  But at least for me, I can do a "mvn install" at
> >> the top level and it works.
> >>
> >> Bng
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > For additional commands, e-mail: users-h...@wicket.apache.org
> >
> >
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

RE: Hibernate - OSIV

[Josh Chappelle]

What error are you getting?

-Original Message-
From: Jeffrey Schneller [mailto:jeffrey.schnel...@envisa.com] 
Sent: Wednesday, March 31, 2010 4:47 PM
To: users@wicket.apache.org
Subject: Hibernate - OSIV 

I think I have the OSIV filter setup correctly but I can't access any lazy
loaded properties of my objects.  I am not even between requests when this
is happening.  Does anyone have any ideas?  I can't seem to figure this out.
I have looked at OSIV in Spring and OSIV in Wicket.  I can't seem to find
any examples that will help me to determine the problem.  I have included
all the code and xml configuration that I believe is relevant.  Any help
would be appreciated.  Also a clean example of how to setup Spring +
Hibernate OSIV in the wiki would be a big help.

 

 

Here is what I have [a very simplified example]:

 

@SpringBean

private IProductDao dao;

 

// the following two lines are in the constructor for the page

Product product = dao.findBySku(sku);

List options = product.getOptions();// this is lazy loaded -
Yes, I know in this example I could just eager fetch it but other times I
don't need the options

 

// a generic dao

public abstract class GenericDao extends
HibernateDaoSupport

 

// the product dao

public class ProductDao extends GenericDao implements IProductDao {

 

wicket-spring-hibernate



contextConfigLocation

 
classpath:resources/applicationContext.xml





 
org.springframework.web.context.ContextLoaderListener





opensessioninview

 
org.springframework.orm.hibernate3.support.OpenSessionInViewFi
lter



 



wicket-spring-hibernate

 
org.apache.wicket.protocol.http.WicketFilter



applicationFactoryClassName

 
org.apache.wicket.spring.SpringWebApplicationFactory





applicationClassName

com.mycompany.WicketApplication





 



opensessioninview

/*



 



wicket-spring-hibernate

/*



 







org.hibernate.dialect.MySQL5Dialect


true





com.mysql.jdbc.Driver


org.hibernate.connection.C3P0Conne
ctionProvider

1

300

1

5

20

1800

50









com.mycompany.entities







 









  

 







 

___ 

Jeffrey A. Schneller

 

Envisa

End-to-End E-Commerce for the Multi-Channel Merchant

 

281 Pleasant Street

Framingham, MA  01701

P: (508) 405-1220 x115

C: (508) 954-8044

F: (508) 405-1219

 



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: RE: Hibernate - OSIV

[James Carman]

Have you tried tuning up logging?  See when the session is being
opened/closed.

On Mar 31, 2010 6:06 PM, "Jeffrey Schneller" 
wrote:

I don't think that is it.  I haven't even put the object into any model yet.
 I am just calling the dao and then calling the getter.  I haven't even
gotten to the point where models would be in use.


-Original Message-
From: jcar...@carmanconsulting.com [mailto:jcar...@carmanconsulting.com]...
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

RE: Hibernate - OSIV

[Jeffrey Schneller]

I don't think that is it.  I haven't even put the object into any model yet.  I 
am just calling the dao and then calling the getter.  I haven't even gotten to 
the point where models would be in use.

-Original Message-
From: jcar...@carmanconsulting.com [mailto:jcar...@carmanconsulting.com] On 
Behalf Of James Carman
Sent: Wednesday, March 31, 2010 5:59 PM
To: users@wicket.apache.org
Subject: Re: Hibernate - OSIV

Loadabledetachablemodel?

On Mar 31, 2010 5:47 PM, "Jeffrey Schneller" 
wrote:

I think I have the OSIV filter setup correctly but I can't access any lazy
loaded properties of my objects.  I am not even between requests when this
is happening.  Does anyone have any ideas?  I can't seem to figure this out.
 I have looked at OSIV in Spring and OSIV in Wicket.  I can't seem to find
any examples that will help me to determine the problem.  I have included
all the code and xml configuration that I believe is relevant.  Any help
would be appreciated.  Also a clean example of how to setup Spring +
Hibernate OSIV in the wiki would be a big help.





Here is what I have [a very simplified example]:



@SpringBean

private IProductDao dao;



// the following two lines are in the constructor for the page

Product product = dao.findBySku(sku);

List options = product.getOptions();// this is lazy loaded -
Yes, I know in this example I could just eager fetch it but other times I
don't need the options



// a generic dao

public abstract class GenericDao extends
HibernateDaoSupport



// the product dao

public class ProductDao extends GenericDao implements IProductDao {



wicket-spring-hibernate

   

   contextConfigLocation

   classpath:resources/applicationContext.xml

   

   


 
org.springframework.web.context.ContextLoaderListener

   

   

   opensessioninview


 
org.springframework.orm.hibernate3.support.OpenSessionInViewFilter

   



   

   wicket-spring-hibernate


 org.apache.wicket.protocol.http.WicketFilter

   

   applicationFactoryClassName


 org.apache.wicket.spring.SpringWebApplicationFactory

   

   

   applicationClassName

   com.mycompany.WicketApplication

   

   



   

   opensessioninview

   /*

   



   

   wicket-spring-hibernate

   /*

   





   

   

   org.hibernate.dialect.MySQL5Dialect

   true



   

   com.mysql.jdbc.Driver

   org.hibernate.connection.C3P0ConnectionProvider

   1

   300

   1

   5

   20

   1800

   50

   

   

   

   

   com.mycompany.entities

   

   

   

   

   

   

   

   





   

   

   



___

Jeffrey A. Schneller



Envisa

End-to-End E-Commerce for the Multi-Channel Merchant



281 Pleasant Street

Framingham, MA  01701

P: (508) 405-1220 x115

C: (508) 954-8044

F: (508) 405-1219

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Hibernate - OSIV

[James Carman]

Loadabledetachablemodel?

On Mar 31, 2010 5:47 PM, "Jeffrey Schneller" 
wrote:

I think I have the OSIV filter setup correctly but I can't access any lazy
loaded properties of my objects.  I am not even between requests when this
is happening.  Does anyone have any ideas?  I can't seem to figure this out.
 I have looked at OSIV in Spring and OSIV in Wicket.  I can't seem to find
any examples that will help me to determine the problem.  I have included
all the code and xml configuration that I believe is relevant.  Any help
would be appreciated.  Also a clean example of how to setup Spring +
Hibernate OSIV in the wiki would be a big help.





Here is what I have [a very simplified example]:



@SpringBean

private IProductDao dao;



// the following two lines are in the constructor for the page

Product product = dao.findBySku(sku);

List options = product.getOptions();// this is lazy loaded -
Yes, I know in this example I could just eager fetch it but other times I
don't need the options



// a generic dao

public abstract class GenericDao extends
HibernateDaoSupport



// the product dao

public class ProductDao extends GenericDao implements IProductDao {



wicket-spring-hibernate

   

   contextConfigLocation

   classpath:resources/applicationContext.xml

   

   


 
org.springframework.web.context.ContextLoaderListener

   

   

   opensessioninview


 
org.springframework.orm.hibernate3.support.OpenSessionInViewFilter

   



   

   wicket-spring-hibernate


 org.apache.wicket.protocol.http.WicketFilter

   

   applicationFactoryClassName


 org.apache.wicket.spring.SpringWebApplicationFactory

   

   

   applicationClassName

   com.mycompany.WicketApplication

   

   



   

   opensessioninview

   /*

   



   

   wicket-spring-hibernate

   /*

   





   

   

   org.hibernate.dialect.MySQL5Dialect

   true



   

   com.mysql.jdbc.Driver

   org.hibernate.connection.C3P0ConnectionProvider

   1

   300

   1

   5

   20

   1800

   50

   

   

   

   

   com.mycompany.entities

   

   

   

   

   

   

   

   





   

   

   



___

Jeffrey A. Schneller



Envisa

End-to-End E-Commerce for the Multi-Channel Merchant



281 Pleasant Street

Framingham, MA  01701

P: (508) 405-1220 x115

C: (508) 954-8044

F: (508) 405-1219

Hibernate - OSIV

[Jeffrey Schneller]

I think I have the OSIV filter setup correctly but I can't access any lazy 
loaded properties of my objects.  I am not even between requests when this is 
happening.  Does anyone have any ideas?  I can't seem to figure this out.  I 
have looked at OSIV in Spring and OSIV in Wicket.  I can't seem to find any 
examples that will help me to determine the problem.  I have included all the 
code and xml configuration that I believe is relevant.  Any help would be 
appreciated.  Also a clean example of how to setup Spring + Hibernate OSIV in 
the wiki would be a big help.

 

 

Here is what I have [a very simplified example]:

 

@SpringBean

private IProductDao dao;

 

// the following two lines are in the constructor for the page

Product product = dao.findBySku(sku);

List options = product.getOptions();// this is lazy loaded - Yes, I 
know in this example I could just eager fetch it but other times I don't need 
the options

 

// a generic dao

public abstract class GenericDao extends 
HibernateDaoSupport

 

// the product dao

public class ProductDao extends GenericDao implements IProductDao {

 

wicket-spring-hibernate



contextConfigLocation

classpath:resources/applicationContext.xml






org.springframework.web.context.ContextLoaderListener





opensessioninview


org.springframework.orm.hibernate3.support.OpenSessionInViewFilter



 



wicket-spring-hibernate


org.apache.wicket.protocol.http.WicketFilter



applicationFactoryClassName


org.apache.wicket.spring.SpringWebApplicationFactory





applicationClassName

com.mycompany.WicketApplication





 



opensessioninview

/*



 



wicket-spring-hibernate

/*



 







org.hibernate.dialect.MySQL5Dialect 

true





com.mysql.jdbc.Driver
  

org.hibernate.connection.C3P0ConnectionProvider

1

300

1

5

20

1800

50









com.mycompany.entities







 









  

 







 

___ 

Jeffrey A. Schneller

 

Envisa

End-to-End E-Commerce for the Multi-Channel Merchant

 

281 Pleasant Street

Framingham, MA  01701

P: (508) 405-1220 x115

C: (508) 954-8044

F: (508) 405-1219

 

ModalWindow insise a cell of AjaxDefaultDataTable can't be closed

[Daniela Valero]

Good afternoon!

I ask for help becouse I have a Ajax data table, inside some links that
shows a ModalWindow, the problem is that I can't close that window.

On Ajax Debug I got this message:
*INFO: *
Ajax GET stopped because of precondition check,
url:?wicket:interface=:27:tabs:panel:panelChild:table:body:rows:3:cells:3:cell:modal::IBehaviorListener:0:-1


I implement a Ajax close button, and call a Javascript code
"window.close()", and I got a WicketExeption

WicketMessage: org.apache.wicket.WicketRuntimeException: component
tabs:panel:panelChild:table:body:rows:3:cells:3:cell:modal:content:form:close
not found on page com.consisint.frontend.pages.Home[id = 27], listener
interface = [RequestListenerInterface
name=IActivePageBehaviorListener, method=public abstract void
org.apache.wicket.behavior.IBehaviorListener.onRequest()]


How can I fix this problem?


-- 
| Daniela Valero

"No hay vientos favorables para quien no sabe a donde quiere ir!

Re: Link to a panel

[Daniela Valero]

I am getting a WicketRunTimeExeption, when trying to close my modal, this is
the message

WicketRuntimeException: component
tabs:panel:panelChild:table:body:rows:7:cells:3:cell:modal:content:form:close
not found on page com.consisint.frontend.pages.Home[id = 0], listener
interface = [Request




The hierachy is like this:

1) Big Parent: home extends WebPage, which contains
   1.2) TabPanel, with 1 child
  1.2.1) Policy extend Panel, here there are another panel
  1.2.1.1) ObjectI, who have a AjaxDefaultDataTable
1.2.1.1.1) Have a Link to a modal

In the modal is the close button.

I undestand this exeption is because, wicket is trying to find my close
button on the table?



I was tying to do the modal content reusable, like this
examplebut
that works only for wicket 1.3.3, on actual version throws
aMarkupNotFoundException. Then I did my close button with the
examples, but I
> forget pass the modal window as parameter to content of modal window.
>
> Now I can close my window naturaly
>
> pd: sorry by my grammar
>
>
>
>
> 2010/3/31 Martin Makundi 
>
>> modal window has a close action:
>>
>>  // On close
>>  modalWindow.close(target);
>>
>>
>> **
>> Martin
>>
>> 2010/3/31 Daniela Valero :
>> > yes
>> >
>> > 2010/3/31 Martin Makundi 
>> >
>> >> Ah.. no need to do anything. Is close button ajax button?
>> >>
>> >> **
>> >> Martin
>> >>
>> >> 2010/3/31 Daniela Valero :
>> >> > Yes, Home is the Page class, it have a TabPanel. In the first tab, i
>> have
>> >> a
>> >> > panel called Policy, there I am calling a ModalWindow, then when the
>> >> close
>> >> > button is clicked I want to get back to my Policy panel.
>> >> >
>> >> > 2010/3/31 Martin Makundi 
>> >> >
>> >> >> ;) ?
>> >> >>
>> >> >> Link to same page? Link to specific tab?
>> >> >>
>> >> >> **
>> >> >> Martin
>> >> >>
>> >> >> 2010/3/31 Daniela Valero :
>> >> >> > Good Afternoon users!
>> >> >> >
>> >> >> > I have a hierachy of panels inside my app, Home is the page, there
>> are
>> >> >> > several childs one of them is a tab panel. I need to set a link to
>> a
>> >> >> panel
>> >> >> > child of home.
>> >> >> >
>> >> >> > how can i do this?
>> >> >> >
>> >> >> > --
>> >> >> > | Daniela Valero
>> >> >> >
>> >> >> > "No hay vientos favorables para quien no sabe a donde quiere ir!
>> >> >> >
>> >> >>
>> >> >>
>> -
>> >> >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> >> >> For additional commands, e-mail: users-h...@wicket.apache.org
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >> > --
>> >> > | Daniela Valero
>> >> >
>> >> > "No hay vientos favorables para quien no sabe a donde quiere ir!
>> >> >
>> >>
>> >> -
>> >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> >> For additional commands, e-mail: users-h...@wicket.apache.org
>> >>
>> >>
>> >
>> >
>> > --
>> > | Daniela Valero
>> >
>> > "No hay vientos favorables para quien no sabe a donde quiere ir!
>> >
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>>
>
>
> --
> | Daniela Valero
>
> "No hay vientos favorables para quien no sabe a donde quiere ir!
>



-- 
| Daniela Valero

"No hay vientos favorables para quien no sabe a donde quiere ir!

Re: Link to a panel

[Daniela Valero]

I was tying to do the modal content reusable, like this
examplebut
that works only for wicket 1.3.3, on actual version throws
aMarkupNotFoundException. Then I did my close button with the
examples, but I
forget pass the modal window as parameter to content of modal window.

Now I can close my window naturaly

pd: sorry by my grammar




2010/3/31 Martin Makundi 

> modal window has a close action:
>
>  // On close
>  modalWindow.close(target);
>
>
> **
> Martin
>
> 2010/3/31 Daniela Valero :
> > yes
> >
> > 2010/3/31 Martin Makundi 
> >
> >> Ah.. no need to do anything. Is close button ajax button?
> >>
> >> **
> >> Martin
> >>
> >> 2010/3/31 Daniela Valero :
> >> > Yes, Home is the Page class, it have a TabPanel. In the first tab, i
> have
> >> a
> >> > panel called Policy, there I am calling a ModalWindow, then when the
> >> close
> >> > button is clicked I want to get back to my Policy panel.
> >> >
> >> > 2010/3/31 Martin Makundi 
> >> >
> >> >> ;) ?
> >> >>
> >> >> Link to same page? Link to specific tab?
> >> >>
> >> >> **
> >> >> Martin
> >> >>
> >> >> 2010/3/31 Daniela Valero :
> >> >> > Good Afternoon users!
> >> >> >
> >> >> > I have a hierachy of panels inside my app, Home is the page, there
> are
> >> >> > several childs one of them is a tab panel. I need to set a link to
> a
> >> >> panel
> >> >> > child of home.
> >> >> >
> >> >> > how can i do this?
> >> >> >
> >> >> > --
> >> >> > | Daniela Valero
> >> >> >
> >> >> > "No hay vientos favorables para quien no sabe a donde quiere ir!
> >> >> >
> >> >>
> >> >> -
> >> >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> >> >> For additional commands, e-mail: users-h...@wicket.apache.org
> >> >>
> >> >>
> >> >
> >> >
> >> > --
> >> > | Daniela Valero
> >> >
> >> > "No hay vientos favorables para quien no sabe a donde quiere ir!
> >> >
> >>
> >> -
> >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> >> For additional commands, e-mail: users-h...@wicket.apache.org
> >>
> >>
> >
> >
> > --
> > | Daniela Valero
> >
> > "No hay vientos favorables para quien no sabe a donde quiere ir!
> >
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>


-- 
| Daniela Valero

"No hay vientos favorables para quien no sabe a donde quiere ir!

Re: Link to a panel

[Martin Makundi]

modal window has a close action:

  // On close
  modalWindow.close(target);


**
Martin

2010/3/31 Daniela Valero :
> yes
>
> 2010/3/31 Martin Makundi 
>
>> Ah.. no need to do anything. Is close button ajax button?
>>
>> **
>> Martin
>>
>> 2010/3/31 Daniela Valero :
>> > Yes, Home is the Page class, it have a TabPanel. In the first tab, i have
>> a
>> > panel called Policy, there I am calling a ModalWindow, then when the
>> close
>> > button is clicked I want to get back to my Policy panel.
>> >
>> > 2010/3/31 Martin Makundi 
>> >
>> >> ;) ?
>> >>
>> >> Link to same page? Link to specific tab?
>> >>
>> >> **
>> >> Martin
>> >>
>> >> 2010/3/31 Daniela Valero :
>> >> > Good Afternoon users!
>> >> >
>> >> > I have a hierachy of panels inside my app, Home is the page, there are
>> >> > several childs one of them is a tab panel. I need to set a link to a
>> >> panel
>> >> > child of home.
>> >> >
>> >> > how can i do this?
>> >> >
>> >> > --
>> >> > | Daniela Valero
>> >> >
>> >> > "No hay vientos favorables para quien no sabe a donde quiere ir!
>> >> >
>> >>
>> >> -
>> >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> >> For additional commands, e-mail: users-h...@wicket.apache.org
>> >>
>> >>
>> >
>> >
>> > --
>> > | Daniela Valero
>> >
>> > "No hay vientos favorables para quien no sabe a donde quiere ir!
>> >
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>>
>
>
> --
> | Daniela Valero
>
> "No hay vientos favorables para quien no sabe a donde quiere ir!
>

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Link to a panel

[Daniela Valero]

yes

2010/3/31 Martin Makundi 

> Ah.. no need to do anything. Is close button ajax button?
>
> **
> Martin
>
> 2010/3/31 Daniela Valero :
> > Yes, Home is the Page class, it have a TabPanel. In the first tab, i have
> a
> > panel called Policy, there I am calling a ModalWindow, then when the
> close
> > button is clicked I want to get back to my Policy panel.
> >
> > 2010/3/31 Martin Makundi 
> >
> >> ;) ?
> >>
> >> Link to same page? Link to specific tab?
> >>
> >> **
> >> Martin
> >>
> >> 2010/3/31 Daniela Valero :
> >> > Good Afternoon users!
> >> >
> >> > I have a hierachy of panels inside my app, Home is the page, there are
> >> > several childs one of them is a tab panel. I need to set a link to a
> >> panel
> >> > child of home.
> >> >
> >> > how can i do this?
> >> >
> >> > --
> >> > | Daniela Valero
> >> >
> >> > "No hay vientos favorables para quien no sabe a donde quiere ir!
> >> >
> >>
> >> -
> >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> >> For additional commands, e-mail: users-h...@wicket.apache.org
> >>
> >>
> >
> >
> > --
> > | Daniela Valero
> >
> > "No hay vientos favorables para quien no sabe a donde quiere ir!
> >
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>


-- 
| Daniela Valero

"No hay vientos favorables para quien no sabe a donde quiere ir!

Re: Link to a panel

[Martin Makundi]

Ah.. no need to do anything. Is close button ajax button?

**
Martin

2010/3/31 Daniela Valero :
> Yes, Home is the Page class, it have a TabPanel. In the first tab, i have a
> panel called Policy, there I am calling a ModalWindow, then when the close
> button is clicked I want to get back to my Policy panel.
>
> 2010/3/31 Martin Makundi 
>
>> ;) ?
>>
>> Link to same page? Link to specific tab?
>>
>> **
>> Martin
>>
>> 2010/3/31 Daniela Valero :
>> > Good Afternoon users!
>> >
>> > I have a hierachy of panels inside my app, Home is the page, there are
>> > several childs one of them is a tab panel. I need to set a link to a
>> panel
>> > child of home.
>> >
>> > how can i do this?
>> >
>> > --
>> > | Daniela Valero
>> >
>> > "No hay vientos favorables para quien no sabe a donde quiere ir!
>> >
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>>
>
>
> --
> | Daniela Valero
>
> "No hay vientos favorables para quien no sabe a donde quiere ir!
>

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Link to a panel

[Daniela Valero]

Yes, Home is the Page class, it have a TabPanel. In the first tab, i have a
panel called Policy, there I am calling a ModalWindow, then when the close
button is clicked I want to get back to my Policy panel.

2010/3/31 Martin Makundi 

> ;) ?
>
> Link to same page? Link to specific tab?
>
> **
> Martin
>
> 2010/3/31 Daniela Valero :
> > Good Afternoon users!
> >
> > I have a hierachy of panels inside my app, Home is the page, there are
> > several childs one of them is a tab panel. I need to set a link to a
> panel
> > child of home.
> >
> > how can i do this?
> >
> > --
> > | Daniela Valero
> >
> > "No hay vientos favorables para quien no sabe a donde quiere ir!
> >
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>


-- 
| Daniela Valero

"No hay vientos favorables para quien no sabe a donde quiere ir!

Re: Link to a panel

[Martin Makundi]

;) ?

Link to same page? Link to specific tab?

**
Martin

2010/3/31 Daniela Valero :
> Good Afternoon users!
>
> I have a hierachy of panels inside my app, Home is the page, there are
> several childs one of them is a tab panel. I need to set a link to a panel
> child of home.
>
> how can i do this?
>
> --
> | Daniela Valero
>
> "No hay vientos favorables para quien no sabe a donde quiere ir!
>

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Link to a panel

[Daniela Valero]

Good Afternoon users!

I have a hierachy of panels inside my app, Home is the page, there are
several childs one of them is a tab panel. I need to set a link to a panel
child of home.

how can i do this?

-- 
| Daniela Valero

"No hay vientos favorables para quien no sabe a donde quiere ir!

Re: possible bug?

[Igor Vaynberg]

the first thing it does is clear the multipart flag, it then tries to
find a multipart component which will set the flag to true again...so
if you remove the component that caused multipart to be true it would
reset before the render

-igor

On Wed, Mar 31, 2010 at 9:40 AM, Vladimir Kovalyuk  wrote:
> It seems the following trick does not work for nested forms:
>
>    protected void onRender(final MarkupStream markupStream)
>    {
>        // clear multipart hint, it will be set if necessary by the visitor
>        this.multiPart &= ~MULTIPART_HINT;
>
>        // Force multi-part on if any child form component is multi-part
>        visitFormComponents(new FormComponent.AbstractVisitor()
>        {
>           �...@override
>            public void onFormComponent(FormComponent formComponent)
>            {
>                if (formComponent.isVisible() &&
> formComponent.isMultiPart())
>                {
>                    multiPart |= MULTIPART_HINT;
>                }
>            }
>        });
>
>        super.onRender(markupStream);
>    }
>
> Since multiPart is serializable it will remember multipart hint for the next
> render on nested form even when the component tree does not contain file
> upload component anymore. As the result the form will be multipart encoded
> (see onComponentTag) but then handled with stardard request handler because
> the hint in nested form is cleared only on its own onRender invocation.
>
> Does it sound like a bug? Should I proceed with creating a test for that?
>

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Wicketstuff updated!

[nino martinez wael]

I guess we could start a branch, called wicketstuff-core-attic. Then
upgrade them to latest wicket version and see if they work and if not,
then remove them. Unless someone wants to fix the errors.

2010/3/28 Major Péter :
> JavaEE-Inject is tested, and OK.
>
> It looks like there are projects, which are depending to a specific
> wicket version (1.4-rc*, 1.4.5):
> * multi-text-input-parent
> * flot-parent/flot
> * flot-parent/flot-examples
> * wicket-html5-parent
> * ddcalendar-parent/ddcalendar
> * ddcalendar-parent/ddcalendar-examples
>
> What's going to happen with them?
>
> Regards,
> Peter
>
> 2010-03-24 22:14 keltezéssel, Boris Goldowsky írta:
>> As discussed, and not hearing any objections, I've updated the
>> wicketstuff-core project to depend on Wicket 1.4.7.  wicketstuff-core's
>> version number is now 1.4.7-SNAPSHOT, and the idea is that people can
>> test it, and barring any major problems it can be released as a stable
>> version 1.4.7 .
>>
>> Now, before people can easily test this, the artifacts need to get into
>> the wicket snapshots maven repository, right?  Can someone with the
>> requisite permissions make this happen?  In the meantime of course
>> people are encouraged to download the projects and build and test them
>> locally.
>>
>> In addition to wicket, the following dependencies were also updated to
>> the latest stable version within the same major version of the project.
>> I did not attempt to move Lucene from version 2.4.1 to 3.0.1, for
>> instance, since more significant changes might be required for this (if
>> any subproject is actually using it).
>>
>>  Jetty: 6.1.22
>>  Lucene: 2.4.1
>>  slf4j: 1.5.11
>>  JUnit: 4.8.1
>>
>> I had to make a couple of changes to get everything to build with the
>> new dependencies (commented out wagon-ssh-external extension from
>> inmethod-grid; added new required constructor argument to two instances
>> of SpringComponentInjector).  People should test the build and make sure
>> these changes are ok.  But at least for me, I can do a "mvn install" at
>> the top level and it works.
>>
>> Bng
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: PageExpiredException - getting this when the session hasn't timeout

[Wayne Pope]

Actually - to be clear - we have 2 tomcat instances on the same
machine, but I don't see this being the issue.

So back to the drawing board again :-(



On Wed, Mar 31, 2010 at 6:27 PM, Richard Wilkinson
 wrote:
> OK, so so long as all cluster machines are running, they will all have the
> same contents in their DiskPageMap, and you should never see the exception,
> however, if one machine goes down for a bit, any pages visited during that
> time will not be transferred to it when it comes back up, meaning that the
> DiskPageMaps can get out of sync.
>
> --
>
> Regards - Richard Wilkinson
> Developer,
> jWeekend: OO & Java Technologies - Development and Training
> http://jWeekend.com
>
> On 31 March 2010 16:14, Martijn Dashorst  wrote:
>
>> The last page is kept in the session such that it is transferred
>> across the cluster. Each node in the cluster should then update the
>> local pagestore with that page. Matej has written quite a bit about
>> this behavior on this list, so searching might help.
>>
>> Martijn
>>
>> On Wed, Mar 31, 2010 at 5:02 PM, Richard Wilkinson
>>  wrote:
>> > afaik, the default SecondLevelCacheSessionStore works by keeping the
>> current
>> > page in session (in memory) and uses DiskPageStore as its second level
>> > cache, which stores all the other pages in a file on disk.
>> >
>> > I don't believe that this DiskPageStore is clustered, because it is an
>> > actual file on the machine.  If this is the case then although the
>> current
>> > page will be clustered by tomcat, the previous pages wont be, so wont be
>> > available on the other machine. This could  cause the exception you are
>> > seeing.
>> >
>> > However that is about the limit of my knowledge on the subject, and maybe
>> > now the DiskPageStore is clusterable.  When I have done clustering in the
>> > past I used a custom session store.
>> >
>> > Also I remember reading that you have to tell tomcat not to keep session
>> > attributes serialized after replication for it to work correctly see [1],
>> > (although that is a few years old)
>> >
>> > [1] - http://old.nabble.com/A-few-clustering-questions-td16993201.html
>> >
>> > --
>> >
>> > Regards - Richard Wilkinson
>> > Developer,
>> > jWeekend: OO & Java Technologies - Development and Training
>> > http://jWeekend.com
>> >
>> > On 31 March 2010 15:40, Wayne Pope 
>> wrote:
>> >
>> >> Thanks for the explanation Richard.
>> >>
>> >> We do have setAutomaticMultiWindowSupport set to false, because when
>> >> we had it set to true we had some problems (I cannot remember what
>> >> exactly - something to do with url mounting I think).
>> >>
>> >> Thing is when I experienced this issue I only had one tab open - it
>> >> may explain some of the other similar exceptions in the log though.
>> >> We're using the default SecondLevelCacheSessionStore.
>> >>
>> >> the plot thickens!
>> >>
>> >>
>> >> On Wed, Mar 31, 2010 at 4:22 PM, Richard Wilkinson
>> >>  wrote:
>> >> > Hi,
>> >> >
>> >> > Ok, anyone else please correct me if i am wrong, but afaik:
>> >> >
>> >> > The pagemap holds a finite number of pages in it, each time you access
>> a
>> >> new
>> >> > page it gets added to the page map, how many pages it holds depends on
>> >> which
>> >> > implementation of page map you are using, which usually depends on
>> which
>> >> > type of session store you are using, but usually pages are evicted
>> from
>> >> the
>> >> > page map on a least recently used basis.
>> >> >
>> >> > If you had 2 tabs open, did a load of stuff on one tab, then went back
>> to
>> >> > the other, it is quite possible the page in the other tab will have
>> been
>> >> > removed from the page map.  However wicket should by default try and
>> >> detect
>> >> > that a new tab is open, and give the other tab a different page map,
>> but
>> >> > this is not completely reliable. Also this can be turned
>> >> > off
>> (application.getPageSettings().setAutomaticMultiWindowSupport(false);
>> >> i
>> >> > think), which maybe you have done.
>> >> >
>> >> > --
>> >> >
>> >> > Regards - Richard Wilkinson
>> >> > Developer,
>> >> > jWeekend: OO & Java Technologies - Development and Training
>> >> > http://jWeekend.com
>> >> >
>> >> >
>> >> > On 31 March 2010 15:02, Wayne Pope 
>> >> wrote:
>> >> >
>> >> >> Hi Richard,
>> >> >>
>> >> >> thanks for the reply.
>> >> >> I'll have a look at trying to make the failover fail again - but the
>> >> >> last time we tested it was working fine so unless there is a core
>> >> >> problem with the apache balancer and tomcat I don't know what I can
>> >> >> do.
>> >> >>
>> >> >>
>> >> >> > There are probably other reasons why you might see a page expired
>> >> >> exception,
>> >> >> > for example if you access so many pages after the page you get the
>> >> >> exception
>> >> >> > on that it is it pushed out of the page map, but unless you can
>> >> reproduce
>> >> >> it
>> >> >> > by going directly a single tomcat instance, it is probably down to
>> the
>> >> >> > clustering.
>> >> >>
>>

possible bug?

[Vladimir Kovalyuk]

It seems the following trick does not work for nested forms:

protected void onRender(final MarkupStream markupStream)
{
// clear multipart hint, it will be set if necessary by the visitor
this.multiPart &= ~MULTIPART_HINT;

// Force multi-part on if any child form component is multi-part
visitFormComponents(new FormComponent.AbstractVisitor()
{
@Override
public void onFormComponent(FormComponent formComponent)
{
if (formComponent.isVisible() &&
formComponent.isMultiPart())
{
multiPart |= MULTIPART_HINT;
}
}
});

super.onRender(markupStream);
}

Since multiPart is serializable it will remember multipart hint for the next
render on nested form even when the component tree does not contain file
upload component anymore. As the result the form will be multipart encoded
(see onComponentTag) but then handled with stardard request handler because
the hint in nested form is cleared only on its own onRender invocation.

Does it sound like a bug? Should I proceed with creating a test for that?

Re: PageExpiredException - getting this when the session hasn't timeout

[Richard Wilkinson]

OK, so so long as all cluster machines are running, they will all have the
same contents in their DiskPageMap, and you should never see the exception,
however, if one machine goes down for a bit, any pages visited during that
time will not be transferred to it when it comes back up, meaning that the
DiskPageMaps can get out of sync.

-- 

Regards - Richard Wilkinson
Developer,
jWeekend: OO & Java Technologies - Development and Training
http://jWeekend.com

On 31 March 2010 16:14, Martijn Dashorst  wrote:

> The last page is kept in the session such that it is transferred
> across the cluster. Each node in the cluster should then update the
> local pagestore with that page. Matej has written quite a bit about
> this behavior on this list, so searching might help.
>
> Martijn
>
> On Wed, Mar 31, 2010 at 5:02 PM, Richard Wilkinson
>  wrote:
> > afaik, the default SecondLevelCacheSessionStore works by keeping the
> current
> > page in session (in memory) and uses DiskPageStore as its second level
> > cache, which stores all the other pages in a file on disk.
> >
> > I don't believe that this DiskPageStore is clustered, because it is an
> > actual file on the machine.  If this is the case then although the
> current
> > page will be clustered by tomcat, the previous pages wont be, so wont be
> > available on the other machine. This could  cause the exception you are
> > seeing.
> >
> > However that is about the limit of my knowledge on the subject, and maybe
> > now the DiskPageStore is clusterable.  When I have done clustering in the
> > past I used a custom session store.
> >
> > Also I remember reading that you have to tell tomcat not to keep session
> > attributes serialized after replication for it to work correctly see [1],
> > (although that is a few years old)
> >
> > [1] - http://old.nabble.com/A-few-clustering-questions-td16993201.html
> >
> > --
> >
> > Regards - Richard Wilkinson
> > Developer,
> > jWeekend: OO & Java Technologies - Development and Training
> > http://jWeekend.com
> >
> > On 31 March 2010 15:40, Wayne Pope 
> wrote:
> >
> >> Thanks for the explanation Richard.
> >>
> >> We do have setAutomaticMultiWindowSupport set to false, because when
> >> we had it set to true we had some problems (I cannot remember what
> >> exactly - something to do with url mounting I think).
> >>
> >> Thing is when I experienced this issue I only had one tab open - it
> >> may explain some of the other similar exceptions in the log though.
> >> We're using the default SecondLevelCacheSessionStore.
> >>
> >> the plot thickens!
> >>
> >>
> >> On Wed, Mar 31, 2010 at 4:22 PM, Richard Wilkinson
> >>  wrote:
> >> > Hi,
> >> >
> >> > Ok, anyone else please correct me if i am wrong, but afaik:
> >> >
> >> > The pagemap holds a finite number of pages in it, each time you access
> a
> >> new
> >> > page it gets added to the page map, how many pages it holds depends on
> >> which
> >> > implementation of page map you are using, which usually depends on
> which
> >> > type of session store you are using, but usually pages are evicted
> from
> >> the
> >> > page map on a least recently used basis.
> >> >
> >> > If you had 2 tabs open, did a load of stuff on one tab, then went back
> to
> >> > the other, it is quite possible the page in the other tab will have
> been
> >> > removed from the page map.  However wicket should by default try and
> >> detect
> >> > that a new tab is open, and give the other tab a different page map,
> but
> >> > this is not completely reliable. Also this can be turned
> >> > off
> (application.getPageSettings().setAutomaticMultiWindowSupport(false);
> >> i
> >> > think), which maybe you have done.
> >> >
> >> > --
> >> >
> >> > Regards - Richard Wilkinson
> >> > Developer,
> >> > jWeekend: OO & Java Technologies - Development and Training
> >> > http://jWeekend.com
> >> >
> >> >
> >> > On 31 March 2010 15:02, Wayne Pope 
> >> wrote:
> >> >
> >> >> Hi Richard,
> >> >>
> >> >> thanks for the reply.
> >> >> I'll have a look at trying to make the failover fail again - but the
> >> >> last time we tested it was working fine so unless there is a core
> >> >> problem with the apache balancer and tomcat I don't know what I can
> >> >> do.
> >> >>
> >> >>
> >> >> > There are probably other reasons why you might see a page expired
> >> >> exception,
> >> >> > for example if you access so many pages after the page you get the
> >> >> exception
> >> >> > on that it is it pushed out of the page map, but unless you can
> >> reproduce
> >> >> it
> >> >> > by going directly a single tomcat instance, it is probably down to
> the
> >> >> > clustering.
> >> >>
> >> >> Problem is I cannot reproduce it at all (and I have tried for quite
> >> >> some time now). Can you explain a little more:
> >> >>
> >> >> >if you access so many pages after the page you get the exception
> >> >> > on that it is it pushed out of the page map,
> >> >>
> >> >> Do you mean if we have 2 tabs open , and on one I move around the
> >> >>

Re: PageExpiredException - getting this when the session hasn't timeout

[Martijn Dashorst]

The last page is kept in the session such that it is transferred
across the cluster. Each node in the cluster should then update the
local pagestore with that page. Matej has written quite a bit about
this behavior on this list, so searching might help.

Martijn

On Wed, Mar 31, 2010 at 5:02 PM, Richard Wilkinson
 wrote:
> afaik, the default SecondLevelCacheSessionStore works by keeping the current
> page in session (in memory) and uses DiskPageStore as its second level
> cache, which stores all the other pages in a file on disk.
>
> I don't believe that this DiskPageStore is clustered, because it is an
> actual file on the machine.  If this is the case then although the current
> page will be clustered by tomcat, the previous pages wont be, so wont be
> available on the other machine. This could  cause the exception you are
> seeing.
>
> However that is about the limit of my knowledge on the subject, and maybe
> now the DiskPageStore is clusterable.  When I have done clustering in the
> past I used a custom session store.
>
> Also I remember reading that you have to tell tomcat not to keep session
> attributes serialized after replication for it to work correctly see [1],
> (although that is a few years old)
>
> [1] - http://old.nabble.com/A-few-clustering-questions-td16993201.html
>
> --
>
> Regards - Richard Wilkinson
> Developer,
> jWeekend: OO & Java Technologies - Development and Training
> http://jWeekend.com
>
> On 31 March 2010 15:40, Wayne Pope  wrote:
>
>> Thanks for the explanation Richard.
>>
>> We do have setAutomaticMultiWindowSupport set to false, because when
>> we had it set to true we had some problems (I cannot remember what
>> exactly - something to do with url mounting I think).
>>
>> Thing is when I experienced this issue I only had one tab open - it
>> may explain some of the other similar exceptions in the log though.
>> We're using the default SecondLevelCacheSessionStore.
>>
>> the plot thickens!
>>
>>
>> On Wed, Mar 31, 2010 at 4:22 PM, Richard Wilkinson
>>  wrote:
>> > Hi,
>> >
>> > Ok, anyone else please correct me if i am wrong, but afaik:
>> >
>> > The pagemap holds a finite number of pages in it, each time you access a
>> new
>> > page it gets added to the page map, how many pages it holds depends on
>> which
>> > implementation of page map you are using, which usually depends on which
>> > type of session store you are using, but usually pages are evicted from
>> the
>> > page map on a least recently used basis.
>> >
>> > If you had 2 tabs open, did a load of stuff on one tab, then went back to
>> > the other, it is quite possible the page in the other tab will have been
>> > removed from the page map.  However wicket should by default try and
>> detect
>> > that a new tab is open, and give the other tab a different page map, but
>> > this is not completely reliable. Also this can be turned
>> > off (application.getPageSettings().setAutomaticMultiWindowSupport(false);
>> i
>> > think), which maybe you have done.
>> >
>> > --
>> >
>> > Regards - Richard Wilkinson
>> > Developer,
>> > jWeekend: OO & Java Technologies - Development and Training
>> > http://jWeekend.com
>> >
>> >
>> > On 31 March 2010 15:02, Wayne Pope 
>> wrote:
>> >
>> >> Hi Richard,
>> >>
>> >> thanks for the reply.
>> >> I'll have a look at trying to make the failover fail again - but the
>> >> last time we tested it was working fine so unless there is a core
>> >> problem with the apache balancer and tomcat I don't know what I can
>> >> do.
>> >>
>> >>
>> >> > There are probably other reasons why you might see a page expired
>> >> exception,
>> >> > for example if you access so many pages after the page you get the
>> >> exception
>> >> > on that it is it pushed out of the page map, but unless you can
>> reproduce
>> >> it
>> >> > by going directly a single tomcat instance, it is probably down to the
>> >> > clustering.
>> >>
>> >> Problem is I cannot reproduce it at all (and I have tried for quite
>> >> some time now). Can you explain a little more:
>> >>
>> >> >if you access so many pages after the page you get the exception
>> >> > on that it is it pushed out of the page map,
>> >>
>> >> Do you mean if we have 2 tabs open , and on one I move around the
>> >> pages then go back to the first tab and try and do something?
>> >>
>> >>
>> >>
>> >>
>> >> On Wed, Mar 31, 2010 at 3:26 PM, Richard Wilkinson
>> >>  wrote:
>> >> > Ok,
>> >> >
>> >> > If you can replicate the problem by the following:
>> >> > 1) shutting down tomcat 1, therefore ensuring that you go to tomcat 2,
>> >> > 2) going to a page on your site (that has some ajax on there),
>> >> > 3) starting up tomcat 1, then shutting down tomcat 2, therefore
>> ensuring
>> >> > that the next request goes to tomcat 1,
>> >> > 4) then make an ajax request on the current page.
>> >> >
>> >> > If you see the page expired then, it probably indicates that your
>> tomcat
>> >> > session clustering is either is not working correctly, or that
>> >> > you don't h

Re: PageExpiredException - getting this when the session hasn't timeout

[Wayne Pope]

> I don't believe that this DiskPageStore is clustered, because it is an
> actual file on the machine.  If this is the case then although the current
> page will be clustered by tomcat, the previous pages wont be, so wont be
> available on the other machine. This could  cause the exception you are
> seeing.


Thanks Richard that was REALLY helpful - I think this could well be
the issue - I had no idea about this and now I think about it I'm
kicking myself. I have a look into this to try and understand it and
do some searches



On Wed, Mar 31, 2010 at 5:02 PM, Richard Wilkinson
 wrote:
> afaik, the default SecondLevelCacheSessionStore works by keeping the current
> page in session (in memory) and uses DiskPageStore as its second level
> cache, which stores all the other pages in a file on disk.
>
> I don't believe that this DiskPageStore is clustered, because it is an
> actual file on the machine.  If this is the case then although the current
> page will be clustered by tomcat, the previous pages wont be, so wont be
> available on the other machine. This could  cause the exception you are
> seeing.
>
> However that is about the limit of my knowledge on the subject, and maybe
> now the DiskPageStore is clusterable.  When I have done clustering in the
> past I used a custom session store.
>
> Also I remember reading that you have to tell tomcat not to keep session
> attributes serialized after replication for it to work correctly see [1],
> (although that is a few years old)
>
> [1] - http://old.nabble.com/A-few-clustering-questions-td16993201.html
>
> --
>
> Regards - Richard Wilkinson
> Developer,
> jWeekend: OO & Java Technologies - Development and Training
> http://jWeekend.com
>
> On 31 March 2010 15:40, Wayne Pope  wrote:
>
>> Thanks for the explanation Richard.
>>
>> We do have setAutomaticMultiWindowSupport set to false, because when
>> we had it set to true we had some problems (I cannot remember what
>> exactly - something to do with url mounting I think).
>>
>> Thing is when I experienced this issue I only had one tab open - it
>> may explain some of the other similar exceptions in the log though.
>> We're using the default SecondLevelCacheSessionStore.
>>
>> the plot thickens!
>>
>>
>> On Wed, Mar 31, 2010 at 4:22 PM, Richard Wilkinson
>>  wrote:
>> > Hi,
>> >
>> > Ok, anyone else please correct me if i am wrong, but afaik:
>> >
>> > The pagemap holds a finite number of pages in it, each time you access a
>> new
>> > page it gets added to the page map, how many pages it holds depends on
>> which
>> > implementation of page map you are using, which usually depends on which
>> > type of session store you are using, but usually pages are evicted from
>> the
>> > page map on a least recently used basis.
>> >
>> > If you had 2 tabs open, did a load of stuff on one tab, then went back to
>> > the other, it is quite possible the page in the other tab will have been
>> > removed from the page map.  However wicket should by default try and
>> detect
>> > that a new tab is open, and give the other tab a different page map, but
>> > this is not completely reliable. Also this can be turned
>> > off (application.getPageSettings().setAutomaticMultiWindowSupport(false);
>> i
>> > think), which maybe you have done.
>> >
>> > --
>> >
>> > Regards - Richard Wilkinson
>> > Developer,
>> > jWeekend: OO & Java Technologies - Development and Training
>> > http://jWeekend.com
>> >
>> >
>> > On 31 March 2010 15:02, Wayne Pope 
>> wrote:
>> >
>> >> Hi Richard,
>> >>
>> >> thanks for the reply.
>> >> I'll have a look at trying to make the failover fail again - but the
>> >> last time we tested it was working fine so unless there is a core
>> >> problem with the apache balancer and tomcat I don't know what I can
>> >> do.
>> >>
>> >>
>> >> > There are probably other reasons why you might see a page expired
>> >> exception,
>> >> > for example if you access so many pages after the page you get the
>> >> exception
>> >> > on that it is it pushed out of the page map, but unless you can
>> reproduce
>> >> it
>> >> > by going directly a single tomcat instance, it is probably down to the
>> >> > clustering.
>> >>
>> >> Problem is I cannot reproduce it at all (and I have tried for quite
>> >> some time now). Can you explain a little more:
>> >>
>> >> >if you access so many pages after the page you get the exception
>> >> > on that it is it pushed out of the page map,
>> >>
>> >> Do you mean if we have 2 tabs open , and on one I move around the
>> >> pages then go back to the first tab and try and do something?
>> >>
>> >>
>> >>
>> >>
>> >> On Wed, Mar 31, 2010 at 3:26 PM, Richard Wilkinson
>> >>  wrote:
>> >> > Ok,
>> >> >
>> >> > If you can replicate the problem by the following:
>> >> > 1) shutting down tomcat 1, therefore ensuring that you go to tomcat 2,
>> >> > 2) going to a page on your site (that has some ajax on there),
>> >> > 3) starting up tomcat 1, then shutting down tomcat 2, therefore
>> ensuring
>> >> > that the n

Re: automatic palette sorting

[robert.mcguinness]

not sure if this is the best solution but this is how we solved it (basically
customized the Palette component to fit our needs).


in palette.js include the following function and call in
Wicket.Palette.updateRecorder and Wicket.Palette.remove

Wicket.Palette.sortOptions=function(box) {
var data = new Array();
for(i = 0; i < box.options.length; i++) {   
data[i] = new Array();
data[i][0] = box.options[i].text;
data[i][1] = box.options[i].value; 
}

data.sort(function(a, b) {
var aa = a[0].toLowerCase();
var bb = b[0].toLowerCase();
return ((aa < bb) ? -1 : ((aa > bb) ? 1 : 0));  
}); 

for(i = 0; i < data.length; i++) {  
var op = new Option(data[i][0], data[i][1]);
box.options[i] = null;
box.options[i] = op;
}   


}
-- 
View this message in context: 
http://old.nabble.com/automatic-palette-sorting-tp28096974p28097306.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: PageExpiredException - getting this when the session hasn't timeout

[Richard Wilkinson]

afaik, the default SecondLevelCacheSessionStore works by keeping the current
page in session (in memory) and uses DiskPageStore as its second level
cache, which stores all the other pages in a file on disk.

I don't believe that this DiskPageStore is clustered, because it is an
actual file on the machine.  If this is the case then although the current
page will be clustered by tomcat, the previous pages wont be, so wont be
available on the other machine. This could  cause the exception you are
seeing.

However that is about the limit of my knowledge on the subject, and maybe
now the DiskPageStore is clusterable.  When I have done clustering in the
past I used a custom session store.

Also I remember reading that you have to tell tomcat not to keep session
attributes serialized after replication for it to work correctly see [1],
(although that is a few years old)

[1] - http://old.nabble.com/A-few-clustering-questions-td16993201.html

-- 

Regards - Richard Wilkinson
Developer,
jWeekend: OO & Java Technologies - Development and Training
http://jWeekend.com

On 31 March 2010 15:40, Wayne Pope  wrote:

> Thanks for the explanation Richard.
>
> We do have setAutomaticMultiWindowSupport set to false, because when
> we had it set to true we had some problems (I cannot remember what
> exactly - something to do with url mounting I think).
>
> Thing is when I experienced this issue I only had one tab open - it
> may explain some of the other similar exceptions in the log though.
> We're using the default SecondLevelCacheSessionStore.
>
> the plot thickens!
>
>
> On Wed, Mar 31, 2010 at 4:22 PM, Richard Wilkinson
>  wrote:
> > Hi,
> >
> > Ok, anyone else please correct me if i am wrong, but afaik:
> >
> > The pagemap holds a finite number of pages in it, each time you access a
> new
> > page it gets added to the page map, how many pages it holds depends on
> which
> > implementation of page map you are using, which usually depends on which
> > type of session store you are using, but usually pages are evicted from
> the
> > page map on a least recently used basis.
> >
> > If you had 2 tabs open, did a load of stuff on one tab, then went back to
> > the other, it is quite possible the page in the other tab will have been
> > removed from the page map.  However wicket should by default try and
> detect
> > that a new tab is open, and give the other tab a different page map, but
> > this is not completely reliable. Also this can be turned
> > off (application.getPageSettings().setAutomaticMultiWindowSupport(false);
> i
> > think), which maybe you have done.
> >
> > --
> >
> > Regards - Richard Wilkinson
> > Developer,
> > jWeekend: OO & Java Technologies - Development and Training
> > http://jWeekend.com
> >
> >
> > On 31 March 2010 15:02, Wayne Pope 
> wrote:
> >
> >> Hi Richard,
> >>
> >> thanks for the reply.
> >> I'll have a look at trying to make the failover fail again - but the
> >> last time we tested it was working fine so unless there is a core
> >> problem with the apache balancer and tomcat I don't know what I can
> >> do.
> >>
> >>
> >> > There are probably other reasons why you might see a page expired
> >> exception,
> >> > for example if you access so many pages after the page you get the
> >> exception
> >> > on that it is it pushed out of the page map, but unless you can
> reproduce
> >> it
> >> > by going directly a single tomcat instance, it is probably down to the
> >> > clustering.
> >>
> >> Problem is I cannot reproduce it at all (and I have tried for quite
> >> some time now). Can you explain a little more:
> >>
> >> >if you access so many pages after the page you get the exception
> >> > on that it is it pushed out of the page map,
> >>
> >> Do you mean if we have 2 tabs open , and on one I move around the
> >> pages then go back to the first tab and try and do something?
> >>
> >>
> >>
> >>
> >> On Wed, Mar 31, 2010 at 3:26 PM, Richard Wilkinson
> >>  wrote:
> >> > Ok,
> >> >
> >> > If you can replicate the problem by the following:
> >> > 1) shutting down tomcat 1, therefore ensuring that you go to tomcat 2,
> >> > 2) going to a page on your site (that has some ajax on there),
> >> > 3) starting up tomcat 1, then shutting down tomcat 2, therefore
> ensuring
> >> > that the next request goes to tomcat 1,
> >> > 4) then make an ajax request on the current page.
> >> >
> >> > If you see the page expired then, it probably indicates that your
> tomcat
> >> > session clustering is either is not working correctly, or that
> >> > you don't have any clustering in place.  Either of these problems will
> >> mean
> >> > that sessions are not shared to the other tomcat.  So whenever apache
> >> > decides not to obey the sticky sessions (which it can do if it cannot
> >> access
> >> > the tomcat it wants to access) your users session (and pagemap) will
> not
> >> > be accessible, so you will see the page expired exception.
> >> >
> >> > You can also replicate this by making apache do 'round robin'
> cluste

automatic palette sorting

[wic...@geofflancaster.com]

Is there a way to automatically sort the available and selected items in a
palette as they are changed?


mail2web.com – What can On Demand Business Solutions do for you?
http://link.mail2web.com/Business/SharePoint



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: PageExpiredException - getting this when the session hasn't timeout

[Wayne Pope]

Thanks for the explanation Richard.

We do have setAutomaticMultiWindowSupport set to false, because when
we had it set to true we had some problems (I cannot remember what
exactly - something to do with url mounting I think).

Thing is when I experienced this issue I only had one tab open - it
may explain some of the other similar exceptions in the log though.
We're using the default SecondLevelCacheSessionStore.

the plot thickens!


On Wed, Mar 31, 2010 at 4:22 PM, Richard Wilkinson
 wrote:
> Hi,
>
> Ok, anyone else please correct me if i am wrong, but afaik:
>
> The pagemap holds a finite number of pages in it, each time you access a new
> page it gets added to the page map, how many pages it holds depends on which
> implementation of page map you are using, which usually depends on which
> type of session store you are using, but usually pages are evicted from the
> page map on a least recently used basis.
>
> If you had 2 tabs open, did a load of stuff on one tab, then went back to
> the other, it is quite possible the page in the other tab will have been
> removed from the page map.  However wicket should by default try and detect
> that a new tab is open, and give the other tab a different page map, but
> this is not completely reliable. Also this can be turned
> off (application.getPageSettings().setAutomaticMultiWindowSupport(false); i
> think), which maybe you have done.
>
> --
>
> Regards - Richard Wilkinson
> Developer,
> jWeekend: OO & Java Technologies - Development and Training
> http://jWeekend.com
>
>
> On 31 March 2010 15:02, Wayne Pope  wrote:
>
>> Hi Richard,
>>
>> thanks for the reply.
>> I'll have a look at trying to make the failover fail again - but the
>> last time we tested it was working fine so unless there is a core
>> problem with the apache balancer and tomcat I don't know what I can
>> do.
>>
>>
>> > There are probably other reasons why you might see a page expired
>> exception,
>> > for example if you access so many pages after the page you get the
>> exception
>> > on that it is it pushed out of the page map, but unless you can reproduce
>> it
>> > by going directly a single tomcat instance, it is probably down to the
>> > clustering.
>>
>> Problem is I cannot reproduce it at all (and I have tried for quite
>> some time now). Can you explain a little more:
>>
>> >if you access so many pages after the page you get the exception
>> > on that it is it pushed out of the page map,
>>
>> Do you mean if we have 2 tabs open , and on one I move around the
>> pages then go back to the first tab and try and do something?
>>
>>
>>
>>
>> On Wed, Mar 31, 2010 at 3:26 PM, Richard Wilkinson
>>  wrote:
>> > Ok,
>> >
>> > If you can replicate the problem by the following:
>> > 1) shutting down tomcat 1, therefore ensuring that you go to tomcat 2,
>> > 2) going to a page on your site (that has some ajax on there),
>> > 3) starting up tomcat 1, then shutting down tomcat 2, therefore ensuring
>> > that the next request goes to tomcat 1,
>> > 4) then make an ajax request on the current page.
>> >
>> > If you see the page expired then, it probably indicates that your tomcat
>> > session clustering is either is not working correctly, or that
>> > you don't have any clustering in place.  Either of these problems will
>> mean
>> > that sessions are not shared to the other tomcat.  So whenever apache
>> > decides not to obey the sticky sessions (which it can do if it cannot
>> access
>> > the tomcat it wants to access) your users session (and pagemap) will not
>> > be accessible, so you will see the page expired exception.
>> >
>> > You can also replicate this by making apache do 'round robin' clustering
>> > since then you are pretty sure that requests will be fired
>> > to different boxes.
>> >
>> > If this is the problem, it will affect all users using your site at the
>> time
>> > (ie they will all experience the exception), so you may want to try and
>> test
>> > away from production if this is a problem for you.
>> >
>> > There are probably other reasons why you might see a page expired
>> exception,
>> > for example if you access so many pages after the page you get the
>> exception
>> > on that it is it pushed out of the page map, but unless you can reproduce
>> it
>> > by going directly a single tomcat instance, it is probably down to the
>> > clustering.
>> >
>> > Hope that helps.
>> >
>> > --
>> > Regards - Richard Wilkinson
>> > Developer,
>> > jWeekend: OO & Java Technologies - Development and Training
>> > http://jWeekend.com
>> >
>> >
>> >
>> >
>> > On 31 March 2010 14:04, Wayne Pope 
>> wrote:
>> >
>> >> Hi Richard
>> >>
>> >> my mistake we have the following setting:
>> >>
>> >> ProxyPass / balancer://cluster/ stickysession=JSESSIONID nofailover=Off
>> >>
>> >> This problem happens from time to time in production with no pattern
>> >> that we can find. We have a 'shared' firewall that hosts the SSL cert,
>> >> going to the apache instance which balances to 2 tomcat instances.
>> >>

Re: A web site developed with Wicket

[Erdinc]

Hi,
I don't think to release the source code of the application for now,  but I am 
trying to collect the techniques I applied in my wicket projects by maintaining 
an open source project - EasyWicket - http://easywicket.sourceforge.net






From: Gustavo Henrique 
To: users@wicket.apache.org
Sent: Wed, March 31, 2010 2:55:20 PM
Subject: Re: A web site developed with Wicket

could you release the wicket code for us?
that would be a great help for the community.

thanks!



  

Re: PageExpiredException - getting this when the session hasn't timeout

[Richard Wilkinson]

Hi,

Ok, anyone else please correct me if i am wrong, but afaik:

The pagemap holds a finite number of pages in it, each time you access a new
page it gets added to the page map, how many pages it holds depends on which
implementation of page map you are using, which usually depends on which
type of session store you are using, but usually pages are evicted from the
page map on a least recently used basis.

If you had 2 tabs open, did a load of stuff on one tab, then went back to
the other, it is quite possible the page in the other tab will have been
removed from the page map.  However wicket should by default try and detect
that a new tab is open, and give the other tab a different page map, but
this is not completely reliable. Also this can be turned
off (application.getPageSettings().setAutomaticMultiWindowSupport(false); i
think), which maybe you have done.

-- 

Regards - Richard Wilkinson
Developer,
jWeekend: OO & Java Technologies - Development and Training
http://jWeekend.com


On 31 March 2010 15:02, Wayne Pope  wrote:

> Hi Richard,
>
> thanks for the reply.
> I'll have a look at trying to make the failover fail again - but the
> last time we tested it was working fine so unless there is a core
> problem with the apache balancer and tomcat I don't know what I can
> do.
>
>
> > There are probably other reasons why you might see a page expired
> exception,
> > for example if you access so many pages after the page you get the
> exception
> > on that it is it pushed out of the page map, but unless you can reproduce
> it
> > by going directly a single tomcat instance, it is probably down to the
> > clustering.
>
> Problem is I cannot reproduce it at all (and I have tried for quite
> some time now). Can you explain a little more:
>
> >if you access so many pages after the page you get the exception
> > on that it is it pushed out of the page map,
>
> Do you mean if we have 2 tabs open , and on one I move around the
> pages then go back to the first tab and try and do something?
>
>
>
>
> On Wed, Mar 31, 2010 at 3:26 PM, Richard Wilkinson
>  wrote:
> > Ok,
> >
> > If you can replicate the problem by the following:
> > 1) shutting down tomcat 1, therefore ensuring that you go to tomcat 2,
> > 2) going to a page on your site (that has some ajax on there),
> > 3) starting up tomcat 1, then shutting down tomcat 2, therefore ensuring
> > that the next request goes to tomcat 1,
> > 4) then make an ajax request on the current page.
> >
> > If you see the page expired then, it probably indicates that your tomcat
> > session clustering is either is not working correctly, or that
> > you don't have any clustering in place.  Either of these problems will
> mean
> > that sessions are not shared to the other tomcat.  So whenever apache
> > decides not to obey the sticky sessions (which it can do if it cannot
> access
> > the tomcat it wants to access) your users session (and pagemap) will not
> > be accessible, so you will see the page expired exception.
> >
> > You can also replicate this by making apache do 'round robin' clustering
> > since then you are pretty sure that requests will be fired
> > to different boxes.
> >
> > If this is the problem, it will affect all users using your site at the
> time
> > (ie they will all experience the exception), so you may want to try and
> test
> > away from production if this is a problem for you.
> >
> > There are probably other reasons why you might see a page expired
> exception,
> > for example if you access so many pages after the page you get the
> exception
> > on that it is it pushed out of the page map, but unless you can reproduce
> it
> > by going directly a single tomcat instance, it is probably down to the
> > clustering.
> >
> > Hope that helps.
> >
> > --
> > Regards - Richard Wilkinson
> > Developer,
> > jWeekend: OO & Java Technologies - Development and Training
> > http://jWeekend.com
> >
> >
> >
> >
> > On 31 March 2010 14:04, Wayne Pope 
> wrote:
> >
> >> Hi Richard
> >>
> >> my mistake we have the following setting:
> >>
> >> ProxyPass / balancer://cluster/ stickysession=JSESSIONID nofailover=Off
> >>
> >> This problem happens from time to time in production with no pattern
> >> that we can find. We have a 'shared' firewall that hosts the SSL cert,
> >> going to the apache instance which balances to 2 tomcat instances.
> >>
> >> I know its happening as I've experienced it myself but there seems no
> >> reason for it. We're using cookie sessions rather than url
> >>
> >>
> >>
> >>
> >> On Wed, Mar 31, 2010 at 2:51 PM, Richard Wilkinson
> >>  wrote:
> >> > Hi Wayne,
> >> >
> >> > As far as I know mod_proxy_balancer does not have sticky sessions on
> by
> >> > default, you have to tell it what cookie to use.  Am am assuming that
> you
> >> > have multiple tomcats (or similar) behind apache, are you using any
> sort
> >> of
> >> > session replication for them?
> >> >
> >> > Does this exception occur when you go directly to tomcat (or whatever
> you
> >> >

Re: PageExpiredException - getting this when the session hasn't timeout

[Wayne Pope]

Hi Richard,

thanks for the reply.
I'll have a look at trying to make the failover fail again - but the
last time we tested it was working fine so unless there is a core
problem with the apache balancer and tomcat I don't know what I can
do.


> There are probably other reasons why you might see a page expired exception,
> for example if you access so many pages after the page you get the exception
> on that it is it pushed out of the page map, but unless you can reproduce it
> by going directly a single tomcat instance, it is probably down to the
> clustering.

Problem is I cannot reproduce it at all (and I have tried for quite
some time now). Can you explain a little more:

>if you access so many pages after the page you get the exception
> on that it is it pushed out of the page map,

Do you mean if we have 2 tabs open , and on one I move around the
pages then go back to the first tab and try and do something?




On Wed, Mar 31, 2010 at 3:26 PM, Richard Wilkinson
 wrote:
> Ok,
>
> If you can replicate the problem by the following:
> 1) shutting down tomcat 1, therefore ensuring that you go to tomcat 2,
> 2) going to a page on your site (that has some ajax on there),
> 3) starting up tomcat 1, then shutting down tomcat 2, therefore ensuring
> that the next request goes to tomcat 1,
> 4) then make an ajax request on the current page.
>
> If you see the page expired then, it probably indicates that your tomcat
> session clustering is either is not working correctly, or that
> you don't have any clustering in place.  Either of these problems will mean
> that sessions are not shared to the other tomcat.  So whenever apache
> decides not to obey the sticky sessions (which it can do if it cannot access
> the tomcat it wants to access) your users session (and pagemap) will not
> be accessible, so you will see the page expired exception.
>
> You can also replicate this by making apache do 'round robin' clustering
> since then you are pretty sure that requests will be fired
> to different boxes.
>
> If this is the problem, it will affect all users using your site at the time
> (ie they will all experience the exception), so you may want to try and test
> away from production if this is a problem for you.
>
> There are probably other reasons why you might see a page expired exception,
> for example if you access so many pages after the page you get the exception
> on that it is it pushed out of the page map, but unless you can reproduce it
> by going directly a single tomcat instance, it is probably down to the
> clustering.
>
> Hope that helps.
>
> --
> Regards - Richard Wilkinson
> Developer,
> jWeekend: OO & Java Technologies - Development and Training
> http://jWeekend.com
>
>
>
>
> On 31 March 2010 14:04, Wayne Pope  wrote:
>
>> Hi Richard
>>
>> my mistake we have the following setting:
>>
>> ProxyPass / balancer://cluster/ stickysession=JSESSIONID nofailover=Off
>>
>> This problem happens from time to time in production with no pattern
>> that we can find. We have a 'shared' firewall that hosts the SSL cert,
>> going to the apache instance which balances to 2 tomcat instances.
>>
>> I know its happening as I've experienced it myself but there seems no
>> reason for it. We're using cookie sessions rather than url
>>
>>
>>
>>
>> On Wed, Mar 31, 2010 at 2:51 PM, Richard Wilkinson
>>  wrote:
>> > Hi Wayne,
>> >
>> > As far as I know mod_proxy_balancer does not have sticky sessions on by
>> > default, you have to tell it what cookie to use.  Am am assuming that you
>> > have multiple tomcats (or similar) behind apache, are you using any sort
>> of
>> > session replication for them?
>> >
>> > Does this exception occur when you go directly to tomcat (or whatever you
>> > are using) and bypass apache, if so then it indicates a different
>> problem.
>> >
>> > --
>> > Regards - Richard Wilkinson
>> > Developer,
>> > jWeekend: OO & Java Technologies - Development and Training
>> > http://jWeekend.com
>> >
>> > On 31 March 2010 13:28, Wayne Pope 
>> wrote:
>> >
>> >> Well as far as I know the default balancer in apache supports this yes.
>> >>
>> >>
>> >>
>> >> On Mon, Mar 29, 2010 at 2:22 PM, Martijn Dashorst
>> >>  wrote:
>> >> > Are you using sticky sessions?
>> >> >
>> >> > Martijn
>> >> >
>> >> > On Fri, Mar 26, 2010 at 5:15 PM, Wayne Pope
>> >> >  wrote:
>> >> >> One more bit of info - it was a ajax request that caused this.
>> >> >>
>> >> >> Any ideas?
>> >> >>
>> >> >>
>> >> >> On Fri, Mar 26, 2010 at 3:42 PM, Wayne Pope <
>> >> waynemailingli...@gmail.com> wrote:
>> >> >>>
>> >> >>>
>> >> >>> oh and I doubled check that all the classes implement Serializable
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>> Wayne Pope-2 wrote:
>> >> 
>> >>  Hi,
>> >> 
>> >>  we're getting this exception in production sometimes, and today I
>> >>  experienced it first hand.
>> >>  We have a session of 60 mins set in the web.xml - however I got
>> this
>> >>  after just 5 mins:
>> >> 
>> >>  o

Re: PageExpiredException - getting this when the session hasn't timeout

[Wayne Pope]

Hi Martin,

I think we can confidently say that its not a serialization issue as
its a very simple component/panel that is used a lot. The
pageexpiredexception I experience on this component was the first time
we'd seen it. We see these exceptions seemlying randomly in the
production logs.



On Wed, Mar 31, 2010 at 3:29 PM, Martijn Dashorst
 wrote:
> Not only all the classes need to implement Serializable, but their
> properties need to be serializable as well...
>
> public class MyFoo implements Serializable
> {
>    private Connection connection = ...
>
> }
>
> is not completely serializable
>
>
> martijn
>
> On Fri, Mar 26, 2010 at 3:42 PM, Wayne Pope  
> wrote:
>>
>>
>> oh and I doubled check that all the classes implement Serializable
>>
>>
>>
>>
>> Wayne Pope-2 wrote:
>>>
>>> Hi,
>>>
>>> we're getting this exception in production sometimes, and today I
>>> experienced it first hand.
>>> We have a session of 60 mins set in the web.xml - however I got this
>>> after just 5 mins:
>>>
>>> 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(WebRequestCycleProcessor.java:197)
>>>         at
>>> hub.app.wicket.app.HubRequestCycleProcessor.resolve(HubRequestCycleProcessor.java:137)
>>>         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(ApplicationFilterChain.java:235)
>>>         at
>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>>>         at
>>> com.wideplay.warp.persist.PersistenceFilter$3.run(PersistenceFilter.java:141)
>>>         at
>>> com.wideplay.warp.persist.internal.Lifecycles.failEarlyAndLeaveNoOneBehind(Lifecycles.java:29)
>>>         at
>>> com.wideplay.warp.persist.PersistenceFilter.doFilter(PersistenceFilter.java:155)
>>>         at
>>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
>>>         at
>>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>>>         at
>>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>>>         at
>>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>>>         at
>>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
>>>         at
>>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>>>         at
>>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>>>         at
>>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
>>>         at
>>> org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>>>         at
>>> org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
>>>         at
>>> org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
>>>         at
>>> org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
>>>         at
>>> org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
>>>         at
>>> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
>>>         at java.lang.Thread.run(Thread.java:619)
>>>
>>>
>>> I honestly don't know where this is coming from.
>>> What can cause this? cookie not being passed? apache proxy balancer not
>>> working?
>>>
>>> Has anyone experienced this?
>>>
>>>
>>> PS HubRequestCycleProcessor is just calling WebRequestCycleProcessor
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>>> For additional commands, e-mail: users-h...@wicket.apache.org
>>>
>>>
>>>
>>
>> --
>> View this message in context: 
>> http://old.nabble.com/PageExpiredException---getting-this-when-the-session-hasn%27t-timeout-tp28043403p28043436.html
>> Sent from the Wicket - User mailing list archive at Nabble.com.
>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>>
>
>
>
> --
> Become a Wicket expert, learn from the best: http://wicketinaction.com
> Apache Wicket 1.4 increases type safety for web applications
> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.4
>
> -
> To unsubsc

Re: PageExpiredException - getting this when the session hasn't timeout

[Martijn Dashorst]

Not only all the classes need to implement Serializable, but their
properties need to be serializable as well...

public class MyFoo implements Serializable
{
private Connection connection = ...

}

is not completely serializable


martijn

On Fri, Mar 26, 2010 at 3:42 PM, Wayne Pope  wrote:
>
>
> oh and I doubled check that all the classes implement Serializable
>
>
>
>
> Wayne Pope-2 wrote:
>>
>> Hi,
>>
>> we're getting this exception in production sometimes, and today I
>> experienced it first hand.
>> We have a session of 60 mins set in the web.xml - however I got this
>> after just 5 mins:
>>
>> 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(WebRequestCycleProcessor.java:197)
>>         at
>> hub.app.wicket.app.HubRequestCycleProcessor.resolve(HubRequestCycleProcessor.java:137)
>>         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(ApplicationFilterChain.java:235)
>>         at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>>         at
>> com.wideplay.warp.persist.PersistenceFilter$3.run(PersistenceFilter.java:141)
>>         at
>> com.wideplay.warp.persist.internal.Lifecycles.failEarlyAndLeaveNoOneBehind(Lifecycles.java:29)
>>         at
>> com.wideplay.warp.persist.PersistenceFilter.doFilter(PersistenceFilter.java:155)
>>         at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
>>         at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>>         at
>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>>         at
>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>>         at
>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
>>         at
>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>>         at
>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>>         at
>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
>>         at
>> org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>>         at
>> org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
>>         at
>> org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
>>         at
>> org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
>>         at
>> org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
>>         at
>> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
>>         at java.lang.Thread.run(Thread.java:619)
>>
>>
>> I honestly don't know where this is coming from.
>> What can cause this? cookie not being passed? apache proxy balancer not
>> working?
>>
>> Has anyone experienced this?
>>
>>
>> PS HubRequestCycleProcessor is just calling WebRequestCycleProcessor
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>>
>>
>
> --
> View this message in context: 
> http://old.nabble.com/PageExpiredException---getting-this-when-the-session-hasn%27t-timeout-tp28043403p28043436.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>



-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.4 increases type safety for web applications
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.4

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: PageExpiredException - getting this when the session hasn't timeout

[Richard Wilkinson]

Ok,

If you can replicate the problem by the following:
1) shutting down tomcat 1, therefore ensuring that you go to tomcat 2,
2) going to a page on your site (that has some ajax on there),
3) starting up tomcat 1, then shutting down tomcat 2, therefore ensuring
that the next request goes to tomcat 1,
4) then make an ajax request on the current page.

If you see the page expired then, it probably indicates that your tomcat
session clustering is either is not working correctly, or that
you don't have any clustering in place.  Either of these problems will mean
that sessions are not shared to the other tomcat.  So whenever apache
decides not to obey the sticky sessions (which it can do if it cannot access
the tomcat it wants to access) your users session (and pagemap) will not
be accessible, so you will see the page expired exception.

You can also replicate this by making apache do 'round robin' clustering
since then you are pretty sure that requests will be fired
to different boxes.

If this is the problem, it will affect all users using your site at the time
(ie they will all experience the exception), so you may want to try and test
away from production if this is a problem for you.

There are probably other reasons why you might see a page expired exception,
for example if you access so many pages after the page you get the exception
on that it is it pushed out of the page map, but unless you can reproduce it
by going directly a single tomcat instance, it is probably down to the
clustering.

Hope that helps.

-- 
Regards - Richard Wilkinson
Developer,
jWeekend: OO & Java Technologies - Development and Training
http://jWeekend.com




On 31 March 2010 14:04, Wayne Pope  wrote:

> Hi Richard
>
> my mistake we have the following setting:
>
> ProxyPass / balancer://cluster/ stickysession=JSESSIONID nofailover=Off
>
> This problem happens from time to time in production with no pattern
> that we can find. We have a 'shared' firewall that hosts the SSL cert,
> going to the apache instance which balances to 2 tomcat instances.
>
> I know its happening as I've experienced it myself but there seems no
> reason for it. We're using cookie sessions rather than url
>
>
>
>
> On Wed, Mar 31, 2010 at 2:51 PM, Richard Wilkinson
>  wrote:
> > Hi Wayne,
> >
> > As far as I know mod_proxy_balancer does not have sticky sessions on by
> > default, you have to tell it what cookie to use.  Am am assuming that you
> > have multiple tomcats (or similar) behind apache, are you using any sort
> of
> > session replication for them?
> >
> > Does this exception occur when you go directly to tomcat (or whatever you
> > are using) and bypass apache, if so then it indicates a different
> problem.
> >
> > --
> > Regards - Richard Wilkinson
> > Developer,
> > jWeekend: OO & Java Technologies - Development and Training
> > http://jWeekend.com
> >
> > On 31 March 2010 13:28, Wayne Pope 
> wrote:
> >
> >> Well as far as I know the default balancer in apache supports this yes.
> >>
> >>
> >>
> >> On Mon, Mar 29, 2010 at 2:22 PM, Martijn Dashorst
> >>  wrote:
> >> > Are you using sticky sessions?
> >> >
> >> > Martijn
> >> >
> >> > On Fri, Mar 26, 2010 at 5:15 PM, Wayne Pope
> >> >  wrote:
> >> >> One more bit of info - it was a ajax request that caused this.
> >> >>
> >> >> Any ideas?
> >> >>
> >> >>
> >> >> On Fri, Mar 26, 2010 at 3:42 PM, Wayne Pope <
> >> waynemailingli...@gmail.com> wrote:
> >> >>>
> >> >>>
> >> >>> oh and I doubled check that all the classes implement Serializable
> >> >>>
> >> >>>
> >> >>>
> >> >>>
> >> >>> Wayne Pope-2 wrote:
> >> 
> >>  Hi,
> >> 
> >>  we're getting this exception in production sometimes, and today I
> >>  experienced it first hand.
> >>  We have a session of 60 mins set in the web.xml - however I got
> this
> >>  after just 5 mins:
> >> 
> >>  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(WebRequestCycleProcessor.java:197)
> >>  at
> >> 
> >>
> hub.app.wicket.app.HubRequestCycleProcessor.resolve(HubRequestCycleProcessor.java:137)
> >>  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(ApplicationFilterChain.java:235)
> >>  at
> >> 
> >>
> org.apache.catalina.core.ApplicationFilterChain.doFilter

Re: Wicket and JEE6

[James Carman]

Ok, I think I've got the conversation stuff working properly.  My
current example is a version of the numberguess game which makes the
"Game" bean a @ConversationScoped object.  It's not a good example of
a "conversation" per se, but I'd like to beef up the example
application to show off more of what CDI can do in the near future.
Please feel free to check it out.  If there is enough interest, I'll
just move this stuff into wicketstuff SVN (and change the package
names), so other folks can contribute.

On Tue, Mar 30, 2010 at 8:54 AM, James Carman
 wrote:
> I think everything I've done is checked in currently.  I'll take a look at
> your patches later and see how things shake out.  One thing I noticed was
> that my beans weren't being picked up from my local project if I didn't
> include a src/main/resources/META-INF/beans.xml file in there.  I guess the
> classpath scanning looks for all of those resources and scans those
> locations only or something.  Again, thanks for taking a look at what I put
> together.  I plan on doing the conversation stuff very soon, so stay tuned.
>
> On Tue, Mar 30, 2010 at 7:43 AM, Cemal Bayramoglu
>  wrote:
>>
>> James,
>>
>> I'm pretty sure "mvn test" ran successfully on all your projects once
>> I patched the POMs.
>> I ran some (maybe not all) of the demo apps too.
>> Send me your patches if you like too (they must not have been deployed
>> yet on Sunday) and I may be able to take another look this evening or
>> tomorrow PM.
>>
>> Regards - Cemal
>> jWeekend
>> OO & Java Technologies, Wicket
>> Consulting, Development, Training
>> http://jWeekend.com
>>
>> On 30 March 2010 12:30, James Carman  wrote:
>> > I was using M4 of OWB, but I had to patch it.  Are you sure it works for
>> > you?  I was getting a NPE.
>> >
>> > On Tue, Mar 30, 2010 at 7:22 AM, Cemal Bayramoglu <
>> > jweekend_for...@cabouge.com> wrote:
>> >
>> >> James,
>> >>
>> >> See the patch below; please double-check but it should be still valid
>> >> if you haven't updated your POMs since Sunday AM your time.
>> >>
>> >> Regards - Cemal
>> >> jWeekend
>> >> OO & Java Technologies, Wicket
>> >> Consulting, Development, Training
>> >> http://jWeekend.com
>> >>
>> >> == PATCH STARTS BELOW =
>> >> Index: pom.xml
>> >> ===
>> >> --- pom.xml     (revision 78)
>> >> +++ pom.xml     (working copy)
>> >> @@ -36,4 +36,22 @@
>> >>             
>> >>         
>> >>     
>> >> +
>> >> +     
>> >> +        
>> >> +            JBoss Repo
>> >> +            http://repository.jboss.com/maven2
>> >> +        
>> >> +
>> >> +         
>> >> +               geronimo-snapshots
>> >> +               Apache Nexus Snapshots
>> >> +
>> >> https://repository.apache.org/content/groups/snapshots-group
>> >> +               
>> >> +                 true
>> >> +               
>> >> +         
>> >> +
>> >> +    
>> >> +
>> >>  
>> >> \ No newline at end of file
>> >> Index: owb/pom.xml
>> >> ===
>> >> --- owb/pom.xml (revision 78)
>> >> +++ owb/pom.xml (working copy)
>> >> @@ -16,11 +16,12 @@
>> >>             wicket-cdi
>> >>             ${project.version}
>> >>         
>> >> -        
>> >> -            org.apache.openwebbeans
>> >> -            openwebbeans-impl
>> >> -            1.0.0-SNAPSHOT
>> >> -        
>> >> +
>> >> +    org.apache.openwebbeans
>> >> +    openwebbeans-impl
>> >> +    1.0.0-M4
>> >> +
>> >> +
>> >>         
>> >>             org.apache.geronimo.specs
>> >>             geronimo-jcdi_1.0_spec
>> >> Index: owb-example/pom.xml
>> >> ===
>> >> --- owb-example/pom.xml (revision 78)
>> >> +++ owb-example/pom.xml (working copy)
>> >> @@ -62,15 +62,11 @@
>> >>             wicket-cdi-owb
>> >>             ${project.version}
>> >>         
>> >> -        
>> >> -            org.apache.openwebbeans
>> >> -            openwebbeans-web
>> >> -            1.0.0-SNAPSHOT
>> >> -        
>> >> +
>> >>         
>> >>             org.apache.openwebbeans
>> >>             openwebbeans-spi
>> >> -            1.0.0-SNAPSHOT
>> >> +            1.0.0-M4
>> >>         
>> >>         
>> >>             org.apache.geronimo.specs
>> >> == END OF PATCH ABOVE 
>> >>
>> >> On 30 March 2010 12:09, James Carman 
>> >> wrote:
>> >> > Cemal,
>> >> >
>> >> > Please feel free to send me a patch if anything looks crazy.  I have
>> >> > had
>> >> a
>> >> > heck of a time getting all this stuff working.  It's a delicate
>> >> > balance
>> >> > (like herding cats)! :)  The OWB folks have checked in my patch to
>> >> > fix
>> >> one
>> >> > of the issues, but we're still hammering out another.
>> >> >
>> >> > Thanks,
>> >> >
>> >> > James
>> >> >
>> >> > On Tue, Mar 30, 2010 at 7:05 AM, Cemal Bayramoglu <
>> >> > jweekend_for...@cabouge.com> wrote:
>> >> >
>> >> >> Oliv

Re: PageExpiredException - getting this when the session hasn't timeout

[Wayne Pope]

Hi Richard

my mistake we have the following setting:

ProxyPass / balancer://cluster/ stickysession=JSESSIONID nofailover=Off

This problem happens from time to time in production with no pattern
that we can find. We have a 'shared' firewall that hosts the SSL cert,
going to the apache instance which balances to 2 tomcat instances.

I know its happening as I've experienced it myself but there seems no
reason for it. We're using cookie sessions rather than url




On Wed, Mar 31, 2010 at 2:51 PM, Richard Wilkinson
 wrote:
> Hi Wayne,
>
> As far as I know mod_proxy_balancer does not have sticky sessions on by
> default, you have to tell it what cookie to use.  Am am assuming that you
> have multiple tomcats (or similar) behind apache, are you using any sort of
> session replication for them?
>
> Does this exception occur when you go directly to tomcat (or whatever you
> are using) and bypass apache, if so then it indicates a different problem.
>
> --
> Regards - Richard Wilkinson
> Developer,
> jWeekend: OO & Java Technologies - Development and Training
> http://jWeekend.com
>
> On 31 March 2010 13:28, Wayne Pope  wrote:
>
>> Well as far as I know the default balancer in apache supports this yes.
>>
>>
>>
>> On Mon, Mar 29, 2010 at 2:22 PM, Martijn Dashorst
>>  wrote:
>> > Are you using sticky sessions?
>> >
>> > Martijn
>> >
>> > On Fri, Mar 26, 2010 at 5:15 PM, Wayne Pope
>> >  wrote:
>> >> One more bit of info - it was a ajax request that caused this.
>> >>
>> >> Any ideas?
>> >>
>> >>
>> >> On Fri, Mar 26, 2010 at 3:42 PM, Wayne Pope <
>> waynemailingli...@gmail.com> wrote:
>> >>>
>> >>>
>> >>> oh and I doubled check that all the classes implement Serializable
>> >>>
>> >>>
>> >>>
>> >>>
>> >>> Wayne Pope-2 wrote:
>> 
>>  Hi,
>> 
>>  we're getting this exception in production sometimes, and today I
>>  experienced it first hand.
>>  We have a session of 60 mins set in the web.xml - however I got this
>>  after just 5 mins:
>> 
>>  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(WebRequestCycleProcessor.java:197)
>>          at
>> 
>> hub.app.wicket.app.HubRequestCycleProcessor.resolve(HubRequestCycleProcessor.java:137)
>>          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(ApplicationFilterChain.java:235)
>>          at
>> 
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>>          at
>> 
>> com.wideplay.warp.persist.PersistenceFilter$3.run(PersistenceFilter.java:141)
>>          at
>> 
>> com.wideplay.warp.persist.internal.Lifecycles.failEarlyAndLeaveNoOneBehind(Lifecycles.java:29)
>>          at
>> 
>> com.wideplay.warp.persist.PersistenceFilter.doFilter(PersistenceFilter.java:155)
>>          at
>> 
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
>>          at
>> 
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>>          at
>> 
>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>>          at
>> 
>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>>          at
>> 
>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
>>          at
>> 
>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>>          at
>> 
>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>>          at
>> 
>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
>>          at
>>  org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>>          at
>>  org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
>>          at
>>  org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
>>          at
>> 
>> org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
>>          at
>> 
>> org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
>>          at
>> 
>> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
>>        

Re: PageExpiredException - getting this when the session hasn't timeout

[Richard Wilkinson]

Hi Wayne,

As far as I know mod_proxy_balancer does not have sticky sessions on by
default, you have to tell it what cookie to use.  Am am assuming that you
have multiple tomcats (or similar) behind apache, are you using any sort of
session replication for them?

Does this exception occur when you go directly to tomcat (or whatever you
are using) and bypass apache, if so then it indicates a different problem.

-- 
Regards - Richard Wilkinson
Developer,
jWeekend: OO & Java Technologies - Development and Training
http://jWeekend.com

On 31 March 2010 13:28, Wayne Pope  wrote:

> Well as far as I know the default balancer in apache supports this yes.
>
>
>
> On Mon, Mar 29, 2010 at 2:22 PM, Martijn Dashorst
>  wrote:
> > Are you using sticky sessions?
> >
> > Martijn
> >
> > On Fri, Mar 26, 2010 at 5:15 PM, Wayne Pope
> >  wrote:
> >> One more bit of info - it was a ajax request that caused this.
> >>
> >> Any ideas?
> >>
> >>
> >> On Fri, Mar 26, 2010 at 3:42 PM, Wayne Pope <
> waynemailingli...@gmail.com> wrote:
> >>>
> >>>
> >>> oh and I doubled check that all the classes implement Serializable
> >>>
> >>>
> >>>
> >>>
> >>> Wayne Pope-2 wrote:
> 
>  Hi,
> 
>  we're getting this exception in production sometimes, and today I
>  experienced it first hand.
>  We have a session of 60 mins set in the web.xml - however I got this
>  after just 5 mins:
> 
>  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(WebRequestCycleProcessor.java:197)
>  at
> 
> hub.app.wicket.app.HubRequestCycleProcessor.resolve(HubRequestCycleProcessor.java:137)
>  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(ApplicationFilterChain.java:235)
>  at
> 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>  at
> 
> com.wideplay.warp.persist.PersistenceFilter$3.run(PersistenceFilter.java:141)
>  at
> 
> com.wideplay.warp.persist.internal.Lifecycles.failEarlyAndLeaveNoOneBehind(Lifecycles.java:29)
>  at
> 
> com.wideplay.warp.persist.PersistenceFilter.doFilter(PersistenceFilter.java:155)
>  at
> 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
>  at
> 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>  at
> 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
>  at
> 
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
>  at
> 
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
>  at
> 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>  at
> 
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>  at
> 
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
>  at
>  org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
>  at
>  org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
>  at
>  org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
>  at
> 
> org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
>  at
> 
> org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
>  at
> 
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
>  at java.lang.Thread.run(Thread.java:619)
> 
> 
>  I honestly don't know where this is coming from.
>  What can cause this? cookie not being passed? apache proxy balancer
> not
>  working?
> 
>  Has anyone experienced this?
> 
> 
>  PS HubRequestCycleProcessor is just calling WebRequestCycleProcessor
> 
>  -
>  To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>  For additional commands, e-mail: users-h...@wicket.apache.org
> 
> 
> 
> >>>
> >>> --
> >>> View this message in context:
> http://old.nabble.com/PageExpir

Re: PageExpiredException - getting this when the session hasn't timeout

[Wayne Pope]

Well as far as I know the default balancer in apache supports this yes.



On Mon, Mar 29, 2010 at 2:22 PM, Martijn Dashorst
 wrote:
> Are you using sticky sessions?
>
> Martijn
>
> On Fri, Mar 26, 2010 at 5:15 PM, Wayne Pope
>  wrote:
>> One more bit of info - it was a ajax request that caused this.
>>
>> Any ideas?
>>
>>
>> On Fri, Mar 26, 2010 at 3:42 PM, Wayne Pope  
>> wrote:
>>>
>>>
>>> oh and I doubled check that all the classes implement Serializable
>>>
>>>
>>>
>>>
>>> Wayne Pope-2 wrote:

 Hi,

 we're getting this exception in production sometimes, and today I
 experienced it first hand.
 We have a session of 60 mins set in the web.xml - however I got this
 after just 5 mins:

 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(WebRequestCycleProcessor.java:197)
         at
 hub.app.wicket.app.HubRequestCycleProcessor.resolve(HubRequestCycleProcessor.java:137)
         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(ApplicationFilterChain.java:235)
         at
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
         at
 com.wideplay.warp.persist.PersistenceFilter$3.run(PersistenceFilter.java:141)
         at
 com.wideplay.warp.persist.internal.Lifecycles.failEarlyAndLeaveNoOneBehind(Lifecycles.java:29)
         at
 com.wideplay.warp.persist.PersistenceFilter.doFilter(PersistenceFilter.java:155)
         at
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
         at
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
         at
 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
         at
 org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
         at
 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
         at
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
         at
 org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
         at
 org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
         at
 org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
         at
 org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
         at
 org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
         at
 org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:698)
         at
 org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:891)
         at
 org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:690)
         at java.lang.Thread.run(Thread.java:619)


 I honestly don't know where this is coming from.
 What can cause this? cookie not being passed? apache proxy balancer not
 working?

 Has anyone experienced this?


 PS HubRequestCycleProcessor is just calling WebRequestCycleProcessor

 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org



>>>
>>> --
>>> View this message in context: 
>>> http://old.nabble.com/PageExpiredException---getting-this-when-the-session-hasn%27t-timeout-tp28043403p28043436.html
>>> Sent from the Wicket - User mailing list archive at Nabble.com.
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>>> For additional commands, e-mail: users-h...@wicket.apache.org
>>>
>>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>>
>>
>
>
>
> --
> Become a Wicket expert, learn from the best: http://wicketinaction.com
> Apache Wicket 1.4 increases type safety for web applications
> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.4
>
> -

Re: A web site developed with Wicket

[Gustavo Henrique]

could you release the wicket code for us?
that would be a great help for the community.

thanks!

Re: Wicket Tester

[svantepower]

lol why didnt I see that.
must be the lack of coffe ;)

Thanks for your help!
-- 
View this message in context: 
http://old.nabble.com/Wicket-Tester-tp28094649p28094705.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Wicket Tester

[Martin Makundi]

Hi!

You must create wickettester with your application.

wickettester = new WicketTester(new MyApplication());


2010/3/31 Svante Reutland :
>
> Hi!im trying to run wicket tester on my application. but I cannot get it to 
> work.this is what I have done so far:
> WicketTester tester = new WicketTester();               
> tester.startPage(Login.class);                  FormTester formTester = 
> tester.newFormTester("loginForm");                      
> formTester.setValue("username", "admin");               
> formTester.setValue("password", "password");                    
> formTester.submit();
> and it gives me an error: cant instantiate constructor and " 
> org.apache.wicket.protocol.http.WebSession cannot be cast to 
> se.project.ui.MySession"
> anyone have any experience with Wicket tester?
> Best RegardsSvante
> _
> Mejla på krogen! Hotmail i mobilen.
> http://new.windowslivemobile.msn.com/SE-SE/windows-live-hotmail/default.aspx

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Wicket Tester

[Svante Reutland]

Hi!im trying to run wicket tester on my application. but I cannot get it to 
work.this is what I have done so far:
WicketTester tester = new WicketTester();   
tester.startPage(Login.class);  FormTester formTester = 
tester.newFormTester("loginForm");  
formTester.setValue("username", "admin");   
formTester.setValue("password", "password");
formTester.submit();
and it gives me an error: cant instantiate constructor and " 
org.apache.wicket.protocol.http.WebSession cannot be cast to 
se.project.ui.MySession"
anyone have any experience with Wicket tester?
Best RegardsSvante
_
Mejla på krogen! Hotmail i mobilen. 
http://new.windowslivemobile.msn.com/SE-SE/windows-live-hotmail/default.aspx

Re: Handling jquery events

[Josh Kamau]

Would you mind to post a code sample?  lets say the javascript event is
"onDrop()"

what do i write on the serverside that will handle the said methods. You can
post an example on the serverside code.


On Wed, Mar 31, 2010 at 12:32 PM, Stefan Lindner wrote:

> Hi Josh,
>
> take a look at the DatePicker class. Ist almost simple. The general way is
> to generate a wicket ajax call and to catch the call in the respond method
> of your AjaxBehavior. The DatePicker responds e.g. to th onclose oder
> onselected method of jQuery-ui-datepicker.
>
> Stefan
>
>
> -Ursprüngliche Nachricht-
> Von: Josh Kamau [mailto:joshnet2...@gmail.com]
> Gesendet: Mittwoch, 31. März 2010 11:26
> An: users@wicket.apache.org
> Betreff: Re: Handling jquery events
>
> Thanks Stefan. i will.
>
> On Wed, Mar 31, 2010 at 12:22 PM, Stefan Lindner  >wrote:
>
> > Hi Josh,
> >
> > take a look at jWicket in wicketstuff core. There you can find a lot of
> > examples how yo can re-act on jQuery events. E.g. ondrop, onresize,
> onclose,
> > onstart...
> >
> > Stefan
> >
> > -Ursprüngliche Nachricht-
> > Von: Josh Kamau [mailto:joshnet2...@gmail.com]
> > Gesendet: Mittwoch, 31. März 2010 11:06
> > An: users@wicket.apache.org
> > Betreff: Handling jquery events
> >
> > Hi Team;
> >
> >  I know i can write java code that handles javascript events e.g
> onChange()
> > using Behaviours. Question: Is there way i can handle in the same way
> > jquery
> > events? or custom javascript events?
> >
> >  Kind regards
> >
> > Josh
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > For additional commands, e-mail: users-h...@wicket.apache.org
> >
> >
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

RE: Handling jquery events

[Stefan Lindner]

Hi Josh,

take a look at the DatePicker class. Ist almost simple. The general way is to 
generate a wicket ajax call and to catch the call in the respond method of your 
AjaxBehavior. The DatePicker responds e.g. to th onclose oder onselected method 
of jQuery-ui-datepicker.

Stefan

 
-Ursprüngliche Nachricht-
Von: Josh Kamau [mailto:joshnet2...@gmail.com] 
Gesendet: Mittwoch, 31. März 2010 11:26
An: users@wicket.apache.org
Betreff: Re: Handling jquery events

Thanks Stefan. i will.

On Wed, Mar 31, 2010 at 12:22 PM, Stefan Lindner wrote:

> Hi Josh,
>
> take a look at jWicket in wicketstuff core. There you can find a lot of
> examples how yo can re-act on jQuery events. E.g. ondrop, onresize, onclose,
> onstart...
>
> Stefan
>
> -Ursprüngliche Nachricht-
> Von: Josh Kamau [mailto:joshnet2...@gmail.com]
> Gesendet: Mittwoch, 31. März 2010 11:06
> An: users@wicket.apache.org
> Betreff: Handling jquery events
>
> Hi Team;
>
>  I know i can write java code that handles javascript events e.g onChange()
> using Behaviours. Question: Is there way i can handle in the same way
> jquery
> events? or custom javascript events?
>
>  Kind regards
>
> Josh
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Handling jquery events

[Josh Kamau]

Thanks Stefan. i will.

On Wed, Mar 31, 2010 at 12:22 PM, Stefan Lindner wrote:

> Hi Josh,
>
> take a look at jWicket in wicketstuff core. There you can find a lot of
> examples how yo can re-act on jQuery events. E.g. ondrop, onresize, onclose,
> onstart...
>
> Stefan
>
> -Ursprüngliche Nachricht-
> Von: Josh Kamau [mailto:joshnet2...@gmail.com]
> Gesendet: Mittwoch, 31. März 2010 11:06
> An: users@wicket.apache.org
> Betreff: Handling jquery events
>
> Hi Team;
>
>  I know i can write java code that handles javascript events e.g onChange()
> using Behaviours. Question: Is there way i can handle in the same way
> jquery
> events? or custom javascript events?
>
>  Kind regards
>
> Josh
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

RE: Handling jquery events

[Stefan Lindner]

Hi Josh,

take a look at jWicket in wicketstuff core. There you can find a lot of 
examples how yo can re-act on jQuery events. E.g. ondrop, onresize, onclose, 
onstart...

Stefan

-Ursprüngliche Nachricht-
Von: Josh Kamau [mailto:joshnet2...@gmail.com] 
Gesendet: Mittwoch, 31. März 2010 11:06
An: users@wicket.apache.org
Betreff: Handling jquery events

Hi Team;

 I know i can write java code that handles javascript events e.g onChange()
using Behaviours. Question: Is there way i can handle in the same way jquery
events? or custom javascript events?

 Kind regards

Josh

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Handling jquery events

[Josh Kamau]

Hi Team;

 I know i can write java code that handles javascript events e.g onChange()
using Behaviours. Question: Is there way i can handle in the same way jquery
events? or custom javascript events?

 Kind regards

Josh

Re: Catch Wicket.Error with FireBug

[MattyDE]

Thanks a lot Perdro!

This works very nice (if u using jQuery):


   $(document).ready( function(){
 WicketAjaxDebug.originalLogError = WicketAjaxDebug.logError;
 WicketAjaxDebug.logError =

function(msg){WicketAjaxDebug.originalLogError(msg);console.error("Wicket: "
+ msg);};  
   }); 
 



Pedro H. O. dos Santos wrote:
> 
> WicketAjaxDebug.original = WicketAjaxDebug.logError;
> WicketAjaxDebug.logError =
> function(msg){WicketAjaxDebug.original(msg);console.log(msg);};
> 
> On Tue, Mar 30, 2010 at 7:11 AM, Martin U
> wrote:
> 
>> Hi Folks,
>>
>>
>> have everyone of you any experience in catching the wicket-ajax and
>> js-errors with the Firebug?
>>
>> Easily we just need to overwrite WicketAjaxDebug.logError... but how?
>>
>>
>> Thanks for any advice!
>>
> 
> 
> 
> -- 
> Pedro Henrique Oliveira dos Santos
> 
> 

-- 
View this message in context: 
http://old.nabble.com/Catch-Wicket.Error-with-FireBug-tp28080433p28092417.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Error reporting on locked page maps, revisited

[Vincent Lussenburg]

Hi all,

I kindly request you to take a look at the following issue:
http://issues.apache.org/jira/browse/WICKET-2796

It's a small issue, but if you like the solution, I'll be happy to create a
patch for it. If not, you can go ahead and close it as a won't-fix ;-).

Kind regards,
Vincent.