> 1. select lists are *much* easier to populate, manipulate, and deal with. ;) > 2. paging and sorting tables/grids/lists are *much, much* easier to > implement, something I wish would be made easier in Wicket. I'd do it > myself if I had time...and tried in the past...but am just not skilled > enough to do yet. > 4. Databinding - sometimes it is nice to set it and forget it...and only use > components when you need it. This of course, is contrary to Wicket...and > differs too much conceptually to do anything about.
I don't know. If we have enough specs/ ideas, there could be a lot of improvements I bet. In general Wicket isn't a declarative framework (and this I believe is where you see the difference?). Which doesn't mean components can never be used declaratively. There are a bunch of possibilities, currently used for things like autolinks, to create such components. > 3. IDE support - both Netbeans and Eclipse have good support for JSF...it'd > be nice if the tools supported the technology in Wicket (convenience stuff). > I haven't tried the eclipse plugin but I'm not sure it would work well w/ a > MyEclipse enterprise project....and I do mostly EJB3.0 architecture. What specific features do you have in mind? One thing that is convenient about Wicket is that it doesn't need a lot of tooling, as it is based on plain Java and HTML. The biggest thing for Wicket is having to synchronize the Java and markup hierarchy. And I think the Wicket plugins for Eclipse, IDEA and Netbeans have at least some support for that. > 5. Seamless capability to go stateless. You that you don't have to be explicit about being stateless? It is 'kind of' implicit now for Wicket (if you create pages without callbacks) and simple to achieve explicitly (overriding getStatelessHint). But I'm afraid that's the best we can do, as Wicket is a stateful framework by default. > 6. I can inject a session bean into a JSF 1.2 managed bean using an @EJB > annoation...quick and simple. I have to use JNDI lookups in Wicket...more > code to manage. > 7. The "model" concept can be tricky in certain cases and isn't intuitive... The old tradeoff thing I'm afraid. Actually, Wicket started (very early version) without the concept of models. But it was introduced soon to deliver flexibility in a consistent way. Please keep feature requests, *and patches* coming and help us improve the areas where we could do better. :) Eelco ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
