The main point for you is the ability to have a service that can provide methods for all the kinds of data that you have. I've no idea of how you're implementing the different kinds of data, so I'll guess one case.
Your different data could decend from the same class, lets say Data. Each implement his difference, like MontlhyData and so on. If this is the case your service could be handle the Data class, or something like this. Explain more about your ideas, what you already did. Regards, --- Felipe Marin Cypriano Vitória - ES On Mon, Feb 16, 2009 at 3:15 AM, Superman859 <[email protected]>wrote: > > I'm working on my first GWT project, which also happens to be somewhat > substantial (at least for me). The project essentially is used for > creating weekly, monthly, midterm, yearly, etc. reports for students. > > The application seems fairly simple as it only seems to consists of > two main things - UI with a bunch of forms and storing / retrieving > that information from a database on the server. > > At first I considered using something as simple as FormPanel, which > would easily allow me to submit information to the server. However, > it needs to be a little more interactive than FormPanel could offer, > in that it needs to be able to pre-populate some data based on what is > currently in the database (thus gathering that data before displaying > the form is needed). > > So I've read up on RPC, and while the process seems easy enough (a lot > to wrap your head around at once, but it's all easy to do individually > I think), it seems a LOT of classes and interfaces must be written. > We need a synchronous and asynchronous interfaces, implementations of > the interface on the server, serializable data objects to pass between > client and server, among others (for example, creating a class with > Facade pattern to make generating and using that RPC proxy easier) - > for each service that we interact with. > > In all, it seems like we are looking at around 5 classes / interfaces > minimum for each service no matter how small or what it does. In my > case, I do the same thing over and over again (either pull some info > from database table, or add to database table), but just using > different data (weekly data, monthly data, midterm data, yearly data, > etc). Does anyone know a better way for me to do this than end up > with tons of small files? > > For example, would it make sense to toss all this into one or two > 'services' thus reducing the amount of files needed for server > interaction? Or, is it standard to go ahead and go through all of > these steps for every single one? Most texts I have read thus far > that explain RPC provide good examples, but they are all separate, > individual examples rather than part of a group of RPC calls. > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
