>If GWT RPC is the way to go then why would someone want to use a helper application like Hibernate? Hibernate is for persistence. GWT-RPC is just a way to communicate client/server, they're not related. You may use both
On Fri, Apr 15, 2011 at 7:55 PM, Mark Wengranowski <[email protected]>wrote: > Hi Jeff, > > > Thanks for the information. > > If GWT RPC is the way to go then why would someone want to use a > helper application like Hibernate? > > One thing im still a little confused on is what you mentioned about > the business logic and not pushing it to the client. I don't want to > push any of the business logic to the client. Presentation and > validation only. I plan on implementing the presentation layer first > as you mentioined but wanted to know what's coding/organizing the > business logic. > > Should i be writing this as completly seperate library contained in a > jar file and include it as a library? Does that mean it will get > pushed to the client? Sorry but im still new to this so im trying to > wrap my head around it. > > Thanks, > -Mark > > On Apr 13, 12:41 pm, Jeff Chimene <[email protected]> wrote: > > On 04/13/2011 10:34 AM,MarkWengranowskiwrote: > > > > > > > > > > > > > Hi Everyone, > > > > > I plan on building the first part of an ERP system for my company and > > > am looking to get some feedback from everyone about different > > > technologies and what I might want to use based on my requirements. > > > > > The Database will be a MS SQL 2008 server and I currently have an old > > > ERP system which contains many years worth of business logic. I plan > > > to utilize some of this via web services and write all the other > > > business logic from scratch. Because this will be the beginning of a > > > new product/program laying out the proper framework and choosing > > > helper utilities is very critical. > > > > > To goal is to have a product that is open multiple implementations. > > > i.e. there could be a GWT program and a seperate JSP/JSF program that > > > will need to share access to the business logic and database. > > > > > My questions are: > > > > > 1. Data access: Should I be setting up something like Hibernate to > > > organize data access? Is there a downside to doing this, i.e. > > > performance? > > > > There's no way to know this answer /a priori/ If this is an important > > question, you'll have to build a proof-of-concept demo. > > > > > What would be the best technology to use with GWT 2.2 > > > that will provide a somewhat future proof/industry standard solution? > > > > GWT RPC works well with standard server solutions. The design is based > > on the fact that the implementor provides the necessary shim code to > > attach the client and server. > > > > > 2. Business logic: Based on my goal of multiple implementations what > > > would be the best way to write my business logic? i.e. create non gwt > > > java classes, create gwt classes, create dll's..... > > > > My advice would be to approach this task by pulling the presentation > > logic out first, and implementing it. Try to resist the inevitable pull > > to move business logic to the client in the first phase. Focus on MVP on > > the client side, you can mock the model as you prove the Presenter/View > > logic. OTOH, there will always be "simple" business logic (e.g. some > > kinds of business-specific validation) You can mock the model that > > supports that kind of validation. > > > > The business logic will be the most expensive logic to reproduce, so I'm > > quite conservative regarding moving this to the client as part of the > > initial work. Develop a plan that includes your representatives from > > your end-user community who will test this in parallel with the existing > > system. > > > > > 3. Frameworks: GWT now has it's own MVP framework. There are a lot of > > > frameworks to choose from and i believe using Googles MVP (Activities > > > and Places) might be the safest way to go for future upgrades to the > > > GWT SDK. Are there any downsides to it and is there a better framework > > > to base a new project on? Will this framework work well with the data > > > access and business logic considerations i mentioned above? > > > > The best answer to this question is to search the list archives for the > > past six months. The GWT implementation of MVP is not your only choice. > > See, for example, the highly regarded gwt-platform. > > > > > 4. Standards: Is there an industry standard for technologies and > > > frameworks to use with GWT 2.2. I know a lot of it depends on your > > > requirements but if we're basing this on a new project with a MS SQL > > > database then???? > > > > I think you'll find gin / guice quite valuable. > > > > > GWT is changing so rapidly that it's hard for me to tell if older > > > suggestions of technologies and frameworks are still valid and good > > > practice with the latest version of GWT. Any help you can give me > > > would be greatly appreciated. > > > > Search within the past six months. Older comments re: > > authentication/authorization are still apropos.- Hide quoted text - > > > > - Show quoted text - > > -- > 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. > > -- Magno Machado Paulo http://blog.magnomachado.com.br http://code.google.com/p/emballo/ -- 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.
