Hello, at the moment I'm writing my diploma-thesis. The project I'm working on is for a big company in germany and consists of porting a Rich-Client-Java-Application to a web-based Application. It should make heavy use of AJAX-Components, because it should behave like the Rich-Client. If the experiences with the prototype turn out satisfactory, the complete application may be ported and maybe other applications will follow.
At the moment I'm thinking about the architecture: From the Rich-Client I will reuse Spring, Hibernate and the Business-Objects, but I'm not sure which Web-Framework to choose from. I have used JSF in former projects and were not happy with it (the Web-Designer thought about committing suicide ;) Well for my thesis I have to give reasons, why I have chosen a specific technology and I have to convince some people, because they have hopes to raise some new projects out of the result of my project. They know about the JSF-Hype, but they don't know about Wicket. I have heared about it 2 weeks ago the first time. I'm doing a comparison between JSF and Wicket. I figured out a lot of disadvantages on JSF-Side, but I have no experience on Wicket-Side and it's disadvantages. I found out that JBoss Seam fixes some bad JSF issues. One guy in my department likes the Google Web Toolkit and is writing a book about it. I'll give it a try. It's a bit like Wicket from the programming style, but it needs a separate compiler and I haven't got a backend solution. I have red that it's possible to use GWT with Wicket. How far is this grown? I fear about a lack of AJAX-Wicket components, because I have seen only few components. I hope someone has experience with similar projects and can give me a few helpful advices. Thanks very much. Patrick --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
