I know i'm a little late on this thread, but as the author of qwicket, i take particular issue with saying because it's "glued with hibernate and spring" that it's no good. The express purpose of qwicket is to create a template for spring/hibernate/wicket based applications. So if it's no good because it uses those, the problem is with you. Blaming a tool built explicitly to leverage those libraries is, to be as blunt as you, stupid. Learn to pick better tools or hire out your work.
On 9/8/07, chickabee <[EMAIL PROTECTED]> wrote: > > > Hi Wicketers, > > I tried wicket today and the example application was up and running on > tomcat in no time, so that was the good part, after that if I like to > create > a sample application on my own then I found no easy way to start. > > Examples are good to browse through and tell about wicket capabilities, > however, not so good from learning point of view, All of the examples are > glued together in one big jar file and it is just not quick enough to > create > a bare-bone application quickly and easily, > > I tried Quicket as mentioned in the readme file, however, Quickets is > nothing but waste of time, because it is glued with Hibernate and Spring > and > both should not be there to start with. > > Not a good experience trying wicket so far, I guess it's the time to try > out > some more simpler app frameworks, > > -Thumbs Down to Wicket! > > -- > View this message in context: > http://www.nabble.com/First-Day-Disgust%21-tf4405663.html#a12568938 > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
