On 2/10/06, VGJ <[EMAIL PROTECTED]> wrote: > I'm trying to decide if I should use Wicket for an e-commerce project here > at work. We're basically going to build a shopping cart which integrates > into existing financial and payment-processing systems that already exist > in-house. > > So, the first things that come to mind are; > > Is Wicket entirely stable when it comes to using Hibernate 3.1.x? Are there > any "gotchas" or serious bugs when interacting w/ Hibernate?
Yep. Gotchas might be that you should use detachable models with Hibernate. But that's all easy enough. > > I'll need to use SSL. I assume Wicket is OK there? Should be fine; some users are using SSL for their Wicket sites, though one user reported an issue for his situation earlier this week. We are currently investigating that, but generally there shouldn't be problems with SSL. If there are, we'll fix it. > I may need to use Crystal Reports (I think there's support for JSP, haven't > researched this much yet, however.) Anyone doing this yet? I'm speaking of > web-based reports (using Crystal Reports 11) - not the actual client > application for reports over the top of an existing database. We have an integration project for JasperReports. Integration for Crystal Reports doesn't exist at this time, but should be easy enough. Look at the jasper reports integration project 'wicket-contrib-jasperreports' that lives in wicket-stuff's cvs to get an idea of how much work this is (not a lot, really) and how to do it. Contribution is welcome :) ! > > Will Wicket scale well enough for thousands of daily users (no real answers > from sales yet on projected # of users and other related info...but I > suspect a few thousand per-day at first.) That all depends on how you plan to scale in the first place. Wicket depends heavily on server side memory, httpsession by default. We've optimized as much as we can, and there are several hooks for further tailoring to specific situations, but if you plan to do httpsession replication, memory usuage is something you want to look at. The good news is that using Wicket should eliminate ad-hoc session usage and thus give a better predictability. If you don't plan to use httpsession clustering, there shouldn't be an issue. And a couple of thousand users a day should be okay without clustering. Best thing is to make the calculations: see what kind of scalability strategy you need, how many users (peak) you expect, how many memory you need for that and how long you want your sessions to be active (the session time out). > Anything else I'm not thinking of? Investigate bookmarkable pages and 'internal pages'. For an e-commerce website, you'll probably need quite a few bookmarkable pages. > So far, I'm completely fascinated w/ Wicket...*finally* someone has their > heads on straight when it comes to web UI building w/ Java...well done! I > would really like to start using it for more projects if all goes well! That's good to hear. Hope it helps you doing your projects, and hope to see you on this list and on the chat channel. Eelco ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
