Well, on my dev machine (my laptop) it's a single cpu 2ghz, 2gb ram. The production server is a dual 3ghz w/ HT proc w/ 4gb ram. Deploying to production takes about 2-3 seconds....it's a blip on the radar.
I'll give the phonebook app a test and let you know. On 6/15/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > > > > Honestly, I haven't had these problems so I can't relate. JBoss > > 4.0.4.GA starts in about 20-30 seconds and deploying the apps I've > > built takes 3-5 sec. roughly. The only descriptor file I've had to > > use so far is a one-liner that maps the URL of the web app to the EAR > > app. You're right, however, you would always deploy-up to JBoss if > > needed but probably not deploy-down from JBoss to a servlet/JSP > > container simply because those services wouldn't be available. > > > well, maybe you have an extremely fast system :) or maybe i am not a very > patient person and go for the solution that takes the least time to startup > even though the difference might be marginal. > > try the wicket-phonebook in contrib and see how fast that starts up. > phonebook has persistence+transactions. id be interested to know how fast it > is on your system. > > -Igor > > > > > _______________________________________________ > Wicket-user mailing list > Wicket-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wicket-user > > > _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
