Can you please explain your changes,
The way request cycles were created was something that annoyed at least some of us for a while. But one of these things that didn't get fixed earlier because the annoyance level wasn't high enough I guess. But this time Jonathan had a good use case. Don't exactly, something with testing. Maybe he'll explain a bit more. Regardless of the immediate practical reasons, the changes were for the better.
one checks in some changes, the other one reverts part of it?
I wouldn't say it's always the ideal way of developing, but this is what has been our development style for long. At least you can state we truly share code ownership. :) Seriously, we've been patching your code, and you ours as well. That's all fine. Sometimes I find communicating via commits even more efficient than explaining what you mean first. I know, that does sound extreme.
Consider that I don't understand what you are changing now, especially in the late stages of the 1.3 release. It's worth an explanation for unexperienced Wicket-deep-internals like me.
I hope http://cwiki.apache.org/WICKET/migrate-13.html#Migrate-1.3-RequestCycle%252CIRequestCycleFactory%252CSession%252CIPageMapandPageMapchanges helps. Eelco
