On Fri, Oct 16, 2009 at 7:52 AM, Jeremy Thomerson <jer...@wickettraining.com > wrote:
> Sorry, that was an overly terse statement. Peter Thomas has put a lot of > work into JTrac, and has done a lot of things that I admire (for instance, > some of his performance testing blog entries, etc). He is also very > helpful > on the mailing list. > > The reason I said not to look at it is that when I was using it, I found > that nearly all of the components were created without the use of models - > "pushing" data into the component rather than making it pull from a model. > While that works fine for a small bug tracker, it would not work well in > most enterprise applications - leading to performance and potentially > memory > issues. > > It's not that it's bad software - but I've taught enough training classes > to > see that one of the most common pitfalls to those new to Wicket is to > always > push data into the models. This works fine in some instances, but is not a > best practice and can lead to a lot of problems later if you don't know > what > you're doing. That's why I said what I did. > > Agreed. JTrac was the first ever Wicket project I attempted, ported the UI over from Spring MVC in a rather short time. It's not as bad as Jeremy makes it out to be though (psst: he's a perfectionist and runs a Wicket training course :P) and I took care to use a detachable model for the primary ListView. JTrac also has a perf-test JMeter script checked-in and users consistently praise the performance. I guess this means that even Wicket apps created by newbies will end up performing rather well. Anyway, here's an open source Wicket application I did recently, which I dare say demonstrates "idiomatic" usage of Wicket models: http://code.google.com/p/perfbench/ > -- > Jeremy Thomerson > http://www.wickettraining.com > > > > On Thu, Oct 15, 2009 at 7:29 PM, Dave B <d...@davebolton.net> wrote: > > > Any particular reason? Form a (very) cursory ten minute look, the > > lack of tests was glaring, though not an indictment of the actual > > Wicket usage. > > > > Thanks, > > Dave > > > > On Fri, Oct 16, 2009 at 11:04 AM, Jeremy Thomerson > > <jer...@wickettraining.com> wrote: > > > Don't look at jtrac..... > > > > > > -- > > > Jeremy Thomerson > > > http://www.wickettraining.com > > > > > > > > > > > > On Thu, Oct 15, 2009 at 6:42 PM, Igor Vaynberg < > igor.vaynb...@gmail.com > > >wrote: > > > > > >> keeping that in mind, > > >> > > >> i wouldnt look at brix, most wicket-related code there has to do with > > >> plumbing and implementing a development model that is unlike wicket > > >> but works better for cmses. > > >> > > >> maybe look at http://www.jtrac.info/ , i think that uses wicket... > > >> > > >> -igor > > >> > > >> On Thu, Oct 15, 2009 at 4:40 PM, Jeremy Thomerson > > >> <jer...@wickettraining.com> wrote: > > >> > Beware - just like any other app, OS or not, you will find OS > projects > > >> out > > >> > there that will teach you all kind of wrong ways to use Wicket. I > > know > > >> of a > > >> > couple because I tried to use them, thinking they would be easier to > > >> build > > >> > on because they used Wicket. But they were so poorly written that > it > > >> would > > >> > be a bad place for someone new to the framework to start. > > >> > > > >> > http://code.google.com/p/brix-cms/ was written by some of the core > > >> > committers, so the Wicket code in it will be good. Not sure how > much > > of > > >> the > > >> > code is actually Wicket specific, though. > > >> > > > >> > -- > > >> > Jeremy Thomerson > > >> > http://www.wickettraining.com > > >> > > > >> > > > >> > > > >> > On Thu, Oct 15, 2009 at 6:35 PM, Dave B <d...@davebolton.net> > wrote: > > >> > > > >> >> Hi, > > >> >> > > >> >> I'm in the process of evaluating Wicket (after an arduous JSF > > project, > > >> >> that has made us re-evaluate our web platform.) > > >> >> > > >> >> I've read Wicket in Action and whole bunch of blog and mailing list > > >> >> posts, done some proof-of-concept work and am now interested in > > >> >> reading source code from a project using Wicket, since I want to > see > > >> >> Wicket in the wild. I know Artifactory uses Wicket, but their > > >> >> Subversion access instructions seem to be out of date. > > >> >> > > >> >> Does anyone know of an open source project using Wicket, so that I > > can > > >> >> peruse the source code? > > >> >> > > >> >> Many thanks, > > >> >> Dave > > >> >> > > >> >> > --------------------------------------------------------------------- > > >> >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > >> >> For additional commands, e-mail: users-h...@wicket.apache.org > > >> >> > > >> >> > > >> > > > >> > > >> --------------------------------------------------------------------- > > >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > >> For additional commands, e-mail: users-h...@wicket.apache.org > > >> > > >> > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > >
