You are missing something here. and that is RPC. Calling get set on your beans will modify that value only in the client browser. You want to communicate this value back to the server. So you need to make an RPC call. Now, you can generate a bean that will make RPC calls in its get set methods... why not? However, there is no such library or framework currently that work this way. With little code, you can create this behaviour. However I will recommend that let a bean be bean. do a rpc when set is called on the bean. Send the entire bean to your service layer. In service layer make the db call.
On Apr 6, 10:32 am, ammours <amer.saifedd...@gmail.com> wrote: > Hello All, > > My goal is to use a developed persistence layer where validation, > fetch , add , update and delete operations are performed with GWT. > This persistence is not EJB, Spring nor hibernate. They are simple > objects doing validations and operations. > > I am looking for a mechanism to pass beans to the UI then making those > beans triggering the persistence layer , pass updates and receive OK > or errors based on the business validation rules. Something like bean > property change fire etc... > > What would be the best direction to follow with GWT? Are there such > examples? Any help is appreciated --~--~---------~--~----~------------~-------~--~----~ 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-Toolkit@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 -~----------~----~----~----~------~----~------~--~---
