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?
I'll need to use SSL. I assume Wicket is OK there?
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.
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.)
Anything else I'm not thinking of?
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!
Thanks!
- [Wicket-user] Wicket for this project?... VGJ
- Re: [Wicket-user] Wicket for this project?... Eelco Hillenius
- Re: [Wicket-user] Wicket for this project?... Martijn Dashorst
- Re: [Wicket-user] Wicket for this project?... Johan Compagner
- Re: [Wicket-user] Wicket for this project?... Piotr Bzdyl
- Re: [Wicket-user] Wicket for this project?..... Martijn Dashorst