Hi, I've seen some examples of using Wicket and I must say it looks nice, clean and simple. I do have some questions I was hoping someone could answer.
I just thought I'd ask about which is the preferred way of learning Wicket 1.4? Personally I've always been a fan of getting a good book, reading it and doing the examples/exercises. As there are only three books published on Wicket, and two of them relates to Wicket 1.3, I'm wondering if there are lots of differences between 1.3 and 1.4 and if I should wait for an updated book? There was some (old) posts about memory problems. I'm planning to write an application which will have roughly 1000 users, the application is pretty simple and they mostly input text into forms and view text from the database. In other words, there won't be much application logic. I was wondering about the current state of Wicket when it comes to performance in terms of CPU and memory usage? How does it compare to using plain Servlets+JSP and how does it compare to JSF? One of the things I liked about the Wicket examples was their simplicity and that it felt you as a developer was in total control of what's going in the output which the client reads. I saw that there are AJAX components now, and I'm wondering when/if I should use them? I was planning to use the JavaScript library jQuery for dynamic content. But when it comes to fetching/posting XML from/to the server that sort of interaction might be best suited for the native components? What I'm afraid of is some sort of situation where I do not control the output as much any more. Should I use Wicket 1.4 instead of 1.3? Lastly I'm wondering about Maven2. I looked at it a while ago but it seemed too complex for me wanting to learn it. Are both ways of retrieving Wicket equal or is there any reason to prefer one of them (maven2/normal jar-download) for me as a user? Thanks for reading my post! Best regards, Kent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
