Creating a GWT runtime configuration in Eclipse
Hi, I am using Eclipse for my GWT project, but it's just a regular Java project. I'd like to turn it into a GWT project so that I can use the Eclipse debugger. I am trying to create a GWT run configuration to accomplish this, but without success. The Main tab in Eclipse's Run Configurations menu has a red cross in it. This probably happens because I selected the wrong class in the 'Main class' field. I selected the EntryPoint class here (in our case our.company.client.Application). At least I think that's what's wrong. Could you help out? What class should I enter in this field? Regards, Julius -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Development time for GWT apps versus 'traditional' MVC with JSP
I think speed will pick up as we move along, because we are both more webapp developers than desktop app developers and certainly for me it took some time to grasp the concept of the event bus, and registering and catching events. So, as Sebastian suggested, the paradigm shift took some time and effort. Secondly, it took time to think about and implement security and to become familiar with UIBinder. We're on a pretty tight schedule and in my view we haven't reserved enough time to get to know the new technology and to learn about third party solutions that can ease development. I don't know any of the solutions (incubatir, bikeshed) Subro mentions. Thanks for sharing your thoughts, J -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Development time for GWT apps versus 'traditional' MVC with JSP
Hi, What are your experiences regarding development time for rich internet applications using GWT compared to the more traditional approach with JSP and an MVC pattern? I am currently developing a RIA with GWT using the MVP pattern illustrated in this article from Google: http://code.google.com/webtoolkit/articles/mvp-architecture.html It took me some time to become familiar with the pattern, with the use of UI Binder and with the general concept of sending back and forth data between the client and the server through RPC. Some of the questions that needed answering in our project so far and that have cost us more time than initially planned are Security: - How to secure services that modify or delete data? Since these services can be called directly from the client they need to be properly secured. For each call we have to verify that the calling user is registered in the database and has the rights to call the service. In order to do this we changed the interface of important services by requiring a valid session key as a parameter. - We now use a servlet filter and go through this process for each view that is loaded on the screen which causes quite a number of requests. Ideally we'd do this only in the outermost view and pass security parameters from the outer most presenter into the constructor of inner presenters. Retrieving text: - When are we going to retrieve texts? Are we going to make a separate call to the database for each presenter/view to load the texts for that presenter/view? Or do we need a mechanism that loads the texts of the entire screen in the outer most presenter, in our case the presenter that belongs to the main grid that is the basis of each screen. Serializing data - We use Hibernate for persistence and had to find a solution for the fact that Hibernate proxy objects are not serializable and have to be converted to serializable POJO's. This was one of the smaller issues. At this moment developing our GWT application is taking us a lot of time. Certainly a lot more than with a traditional JSP approach. I understand that building an application with JSP results in a traditional website, which is different from building a GWT application, which is comparable to creating a desktop application that runs in a browser. It is however taking us about twice as much time to build the same functionality with GWT. What are your experiences? Do you find it more time consuming to build the same functionality with GWT compared to building it with JSP/PHP/ etc and a MVC pattern? We might just be struggling with the new technology and I hope development spedd will pick up as the project progresses, but right now, I am a bit disappointed about the larhe number of hours we're burning answering all sorts of questions and solving all sorts of problems we hadn't seen coming when we started. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT Rocks!
Hi, I just opened a new thread where I ask about experiences with the development time needed for GWT apps compared to traditional JSP web apps. Our experience so far, after 5 weeks, is that it is taking us much more time developing with GWT than developing a webapp with JSP. It might just be our lack of experience and the fact that GWT, the MVP pattern and UIBinder combined present quite a learning curve. http://groups.google.com/group/google-web-toolkit/browse_thread/thread/4495827dc2e82816# We are building a large application that suggests training options and growth paths to employees based on work experience, education, courses done in the past, reviews, etc. It's quite a complex application and we're only just laying out the foundations, that is data retrieval, storage, user, roles, rights, etc. We haven't even started on the real core of the application. On Jul 29, 4:56 am, sakesun roykiatisak sake...@gmail.com wrote: Besides praising, could anybody please give some short story of your experience with GWT ? What kind of project are you working on ? How large is the project team? What is the typical work process ? What tool do you find essential in working with GWT ? Does GWT compile speed cause you any inconvenience ? I'm merely a antique desktop application developer who looking for a sane method to develop boring, enterprise-like, web-based, database application. I've tried a lot of stuffs, but none seem to convince me that my quality of life will be better than using my age old tools. Thanks -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Storing an object at the client during a request
Hello, How can I store an object on the client side during an entire request and make it accessible to multiple presenters in a MVP application? I am currently retrieving the User object in a servlet filter and putting it on the request, like so // get User by cookie User user = sercurityService.getCurrentUser(); // Add to request req.setAttribute(user, user); // Go ahead chain.doFilter(req, res); So, how would I now store it on the client side and access it from my presenters? Best, S -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
