Look in your page spec or template for a binding like map.areaCode. It sounds like you have a hashmap with an areaCode key, and the map isn't declared persistent. Or pehaps it's being nullified in the first submit. When the second submit comes along, the page is trying to store the areaCode in a null map.
Christian Mittendorf wrote: > Hello! > > Using a double-click for selecting buttons is - as far as I can tell > from my observations - a common "mistake" of computer beginners. I > know a number of new computer users, that apply this pattern - which > they know from the desktop for opening files - to navigating web > pages and submitting web forms. > > We are tracking the exceptions from our live applications and there > is one exception, that we really couldn't either recreate with our > test environment nor could we explain it. Probably we have found a > hint now... > > The error is always (better very often) a null pointer exception with > an error message like this: > > target is null for setProperty(null, "areaCode", 040) > > While developing a new application I accidentally did a fast double > click on a button and I got the error message shown above. I was also > able to reproduce this exception, although it wasn't always the same > property that did cause the exception. > > Has anybody else experienced something similar? What is the cause for > this exception? I assume that it must have something to do with the > rewind cycle. Any ideas for my next steps to hunt down this "bug" are > appreciated ;-) > > Christian > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
