1) Generifying* Wicket
[X] Can best be done like currently in the 1.4 branch, where models
and components are both generified. I care most about the improved
static type checking generified models and components give Wicket.
2) How strongly do you feel about your choice above?
[X] Whatever
Just to quickly weigh in on the verbosity argument:As someone who has coded Java (and Perl, C++, etc) in every environment from individual projects to multinational finance systems, I will say that verbosity of code runs a far, far, distant third (or twentieth) to:1. Readability/Understandability,
Hi there,
I'm writing a wicket template that produces a KML document, and it
won't let me add labels or resolve component wicket:id within the KML
Style tag. D'oh!
I'm assuming this is a hangover from the HTML world.
My KML snippet:
!-- styles for every user --
Style
+1, Wicket 1.4 is 1.3 + generics, drop support for 1.3On 18/03/2008, at 3:35 AM, Jeremy Thomerson wrote:+1, Wicket 1.4 is 1.3 + generics, drop support for 1.3On Mon, Mar 17, 2008 at 3:13 AM, Martijn Dashorst [EMAIL PROTECTED] wrote:This thread is for voting only. Use the [discuss] thread for
I am currently having great fun (no, I'm not being sarcastic) with Wicket's IInitializer plugin mechanism, using it to plug additional functionality into a basic CMS framework (e.g. news feeds, video upload, etc). Just hit a brick wall though - it seems as through the initializers are called too
I blogged this, and Eelco wisely suggested I post it here. This is both a warning and plea for help - what's the best way to configure Tomcat on Debian for Wicket?Was up until 3am last night banging my head against another frustrating go-nowhere issue deploying Wicket on Debian Etch’s default
