Frank Bille wrote:
On 1/22/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
this api is simply too fragile. any custom requesttarget impl has to call
this in order for it to be consistent, and if its not consistent its
useless.
+1 because of fragile api.
+1
This is currently biting me for AJAX
Martijn Dashorst wrote:
Our current Wicket release distribution consists of several zip files,
[...]
Wheee, this is almost getting religious. :)
Maven 2 users just, errr, use Maven 2. :)
So for the others, I'd have thought it simplest to have a single zip/tgz
download containing the wicket
Hi,
I have been looking for references on Wicket and OSGi and all solutions I
have seen make use of the WicketServlet (since OSGi HTTP Service only
allows to register servlets) . But now the preferred way to use Wicket is
via a WicketFilter instead of WicketServlet (which his now deprecated,
yes we are aware of this, and yes we plan on supporting the servlet for
osgi. that message is there to let our web users know to use the filter
instead, feel free to ignore it. if you look closer, even though the message
says its deprecated, the class carries no @deprecated annotation. as
