ClassCastException in BehaviorRequestTarget

I've run across a couple of strange ClassCastExceptions in our logs re: the HeaderContributor: java.lang.ClassCastException: org.apache.wicket.behavior.HeaderContributor at org.apache.wicket.request.target.component.listener.BehaviorRequestTarget.processEvents(BehaviorRequestTarget.java:91)

Re: java.util.ConcurrentModificationException inorg.apache.wicket.protocol.http.SecondLevelCacheSessionStore$SecondLevelCachePageMap.put

zation is done in request thread and > pagemap is locked during request. > > -Matej > > On Thu, Dec 18, 2008 at 2:35 PM, leok wrote: >> >> Interesting. I wonder if this error occurs when page components are being >> modified by Ajax while being serialized, e.g. pa

Re: java.util.ConcurrentModificationException inorg.apache.wicket.protocol.http.SecondLevelCacheSessionStore$SecondLevelCachePageMap.put

onsistent state? Xhelas wrote: > > Same symptoms using wocket 1.4-rc1. > > Regards > > Alexandre > > > leok wrote: >> >> I was poking through some logs, and I noticed a few rare instances of >> this exception: >> >> java

java.util.ConcurrentModificationException inorg.apache.wicket.protocol.http.SecondLevelCacheSessionStore$SecondLevelCachePageMap.put

I was poking through some logs, and I noticed a few rare instances of this exception: java.util.ConcurrentModificationException at java.util.LinkedHashMap$LinkedHashIterator.nextEntry(LinkedHashMap.java:365) at java.util.LinkedHashMap$KeyIterator.next(LinkedHashMap.java:376) at java.util.Ha

Re: SpringBeanLocator and @SpringBean performance issue

ally build our own applicationcontext > > > -igor > > On Thu, Dec 11, 2008 at 1:33 PM, leok wrote: >> >> Hello, >> >> Our Wicket app makes use of the @SpringBean annotation thorughout our >> code, >> which is a pretty cool feature. While checking so

Re: SpringBeanLocator and @SpringBean performance issue

nces > as well and essentially build our own applicationcontext > > > -igor > > On Thu, Dec 11, 2008 at 1:33 PM, leok wrote: >> >> Hello, >> >> Our Wicket app makes use of the @SpringBean annotation thorughout our >> code, >> which is a pre

SpringBeanLocator and @SpringBean performance issue

Hello, Our Wicket app makes use of the @SpringBean annotation thorughout our code, which is a pretty cool feature. While checking some thread stack traces during load testing, we found lots of threads bottlenecking in the SpringBeanLocator class: Object blocked: 145.133 ms, Object wait: 0 ms, CP

Re: Graceful handling of ajax after session expiration

containing page could be created if the page didn't exist in the PageMap? leok wrote: > > Thanks for the response! I'm not sure if this solves my problem though, or > if I understand this correctly. Even if I use HybridUrlCodingStrategy to > mount the page, I will still get r

Re: Graceful handling of ajax after session expiration

ance used at http://thoof.com > > The url becomes bookmarkable, and has the page nr and version number > encoded in the url, but wicket will use the bookmarkable part when > there is not session. > > Martijn > > On 10/3/07, leok <[EMAIL PROTECTED]> wrote: >> >

Graceful handling of ajax after session expiration

Hi there - I'm trying to add some graceful handling of ajax behavior during session expiration in my Wicket webapp. Is there a way to not redirect to the session expired page and invoke some other handler, using either a wicket component and/or javascript function, after the session has expired?

Re: @SpringBean and serialization checker

the top of my head right now... > > -igor > > On 9/6/07, leok <[EMAIL PROTECTED]> wrote: >> >> >> Hi, >> >> I'm using the @SpringBean + SpringComponentInjector to inject daos in my >> Wicket web pages. Wi

@SpringBean and serialization checker

Hi, I'm using the @SpringBean + SpringComponentInjector to inject daos in my Wicket web pages. With Wicket 1.3b3, I'm noticing the following exception in my Tomcat (v6.0.13) logs: org.apache.wicket.util.io.SerializableChecker$WicketNotSerializableException: Unable to serialize class: org.apache.