Could you elaborate on what is lacking in Wicket when referring to the back button support (when compared to GWT)? I was under the impression that Wicket had robust back button support?
-----Original Message----- From: Eelco Hillenius [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 28, 2007 1:56 PM To: [email protected] Subject: Re: Is Wicket a proper framework for a Webshop ? It sounds to me like GWT might be a better choice, especially if you need Ajax & robust back button support. Wicket is a good choice when you need a mixed approach. I don't think SpringMVC would be a better choice in any way. Eelco On 8/28/07, neekibo <[EMAIL PROTECTED]> wrote: > > Hi all Wicket-users! > > I am new to web development and so to Wicket. I'm searching for a/the > suitable framework for my case. > > So here a few constrains: > - A webshop with lots of products and categories > - Integration with SpringCore and Hibernate > - Ajax-Magic for a fast responding UI and Drag'n'Drop > > And a few misgivings: > 1.) A component framework is overhead for a webshop (mostly simple > db-read-access operations without a state). A request/response-driven > framework fits better in this context. > 2.) I need standard back and forth browser behaviour. Is this easy to > achieve (with ajax in mind) ? > 3.) Security: I need to easy code "sign in" and secure the payment process > (ssl over http is guess) > 4.) Performance/Scalability. I know, in general the DB is the bottleneck > but ... compared to action-based frameworks. I read somewhere that Wicket is > much faster that JSF, so this seems good to me. > > So these are just a few thoughts, I'm a new to this topic, so pardon me if > something is wrong. In the moment my alternative is SpringMVC. But the > concepts of Wicket appeals to me. Especially the complete lack of JSPs. > > Thanks in advance > Paul > -- > View this message in context: > http://www.nabble.com/Is-Wicket-a-proper-framework-for-a-Webshop---tf4341788.html#a12368098 > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
