On 2/10/06, VGJ <[EMAIL PROTECTED]> wrote: > Is Wicket entirely stable when it comes to using Hibernate 3.1.x? Are there > any "gotchas" or serious bugs when interacting w/ Hibernate?
There are no gotchas or bugs that come to mind. Perhaps you want to use spring in conjunction, and then I would like to point you to our excellent, but under documented spring packages, which are (unfortunately) only available through CVS. I'll be building an alpha release this weekend, and I strive to release the spring packages also. > I'll need to use SSL. I assume Wicket is OK there? There have been some problems with SSL, but as far as I know, they have been resolved. There is one discussion currently active and you may want to search the mail archives for more information. > 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. There is no crystal reports integration available from our projects (wicket-core and wicket-stuff). CR is a commercial offering, so we probably aren't allowed to host the actual CR libraries. There is a JasperReports component library, hosted at the Wicket Stuff project, check the CVS module for that. In my project at Topicus, we'll probably end up using Eclipse BIRT, so we might donate some integration stuff which results from that. There is also another company that probably is going to build upon Crystal Reports. I don't know their status yet. I'll ask around, perhaps both companies can share the effort for the report generation thing. > 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.) Wicket isn't the problem here. I've run several performance tests on our application and on very cheap hardware (2 boxes of $700 each), and untuned database and application server, we get 40 requests per second out of the box with 100 concurrent users, constantly pounding, without pause. We run with the default tomcat settings. The only thing we adjusted was to provide tomcat with more memory 512MB heap, iirc). We haven't done tests with more memory and more tuning of the tomcat server. Another project, TeachScape, done by other committers of the Wicket framework will have about 65000 users (not concurrent). It provides an e-learning environment for the users and is quite large scale. > Anything else I'm not thinking of? Choose what you think best. Many have voiced concerns about our usage of the session. Usually this is a knee-jerk reaction which is very uninformed. However, session size /is/ a concern for all web applications, not just those built with Wicket. Not using Wicket won't automatically guarantee minimal session size, nor a well thought out use of it. In my opinion the idea behind Wicket of storing things into the server session makes for very secure web applications. The fact that nobody can change my customer id, or product id in the request parameters gives a lot of comfort. For financial and privacy sensitive applications this is a very big bonus, which one can't choose to ignore. The component model of Wicket makes it /very/ easy to create application specific components, which enable reuse to the max. Today I created a form component that is Hibernate optimistic locking aware with about (give or take) 20 lines of code. All my collegues need to do now is to subclass VersionedForm instead of plain vanilla Form and bingo: their form uses optimistic locking. And I have done similar components that normally would be very hard to create. Wicket has a lot of promise: you are allowed to write very nice and good object oriented code, and it is harder to write procedural code using Wicket as your web framework. However, it is still possible to create maintenance unfriendly code. You still need decent developers with a good understanding of OO concepts. The performance of the framework itself is solid, and with 1.2 underway, it will only get better. The documentation is getting there, but still very scattered and under par. We are in the process of writing a book (Wicket in Action) which is due late this summer. Probably the book will be available in the Manning early access program. Our community is great: if you have a problem, usually you have an answer within an hour, sometimes within minutes. A solution for bugs usually is also available within a couple of hours. For a project that is completely volunteer work, I think it is one of the best out there. ##wicket on irc.freenode.net is a bit chaotic, but usually very friendly and helpful. Very useful to learn things. > 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! I am using it daily on a project and everytime I get amazed by how powerful it is. Best regards, Martijn -- Living a wicket life... Martijn Dashorst - http://www.jroller.com/page/dashorst Wicket 1.1.1 is out: http://wicket.sourceforge.net/wicket-1.1 ------------------------------------------------------- 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
