http://wicket-stuff.svn.sourceforge.net/viewvc/wicket-stuff/trunk/wicket-contrib-scriptaculous/src/java/org/wicketstuff/scriptaculous/ScriptaculousRequestTarget.java?revision=2024&view=markup
I have been backporting features from the 2.0 branch to the new trunk
and came across this very odd class
we listed the microsoft naming convention (Wicket 2007)
but skipped right over sun's naming conventions! what about
"Apache Wicket SE 6u1" or "Apache Wicket W2SE 6.0 WDK"
[X] Apache Wicket 2.0
the requirement of JDK 1.5 is actually a major shift for
users even if it doesn't break APIs. i als
[ ] Apache Wicket 1.4
Binding: Al Maw
Non binding: Jean Baptiste Quenot, Charlie Dobbie
3 +1
[ ] Apache Wicket 1.5 (after the JDK)
Binding: Johan
Non Binding: Erik van Oosten
2 +1
[ ] Apache Wicket 2.0 (i.e. becomes our old 2.0 minus the c'tor change)
Binding: Martijn, Igor, Frank, Eelco,
Fixed the page expired problem in the clock example.
-Matej
On 4/28/07, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote:
* Juergen Donnerstag:
> I went through the 1.3 examples and seems to me that some are broken
>
> authorization: endless loop of exceptions
Cannot reproduce, maybe fixed by au