the ideal of of "one class that rules them all" may sound great at first, especially if your'e coming of plain old server side where you use spring hibernate and what not, and you take for granted that hibernate does behind the scenes.
but in gwt, you have to be painfully aware of this. the main reason any persistence proxies your pojo's is to track the changes your'e making, no proxies no change tracking, and that's a huge deal, problem as everyone mentioned here that proxies can't leave in the client side, so you can't track changes,. but using gilead for this thing is not exactly the golden solution, (not that there is one mind you), gilead uses beanlib behind the scenes, and that's a framework for object graph CLONE (it's grand i've workd with it before) ,but you should be aware the cloning a complex graph of objects may cause a problem in the future, as you try to attach the graph to the session for persistence. this is because hibernate may tend to load objects using the session, that you haven't attached yet, thus making the way for the infamous NonUniqueObjectException. aside from that, gilead currently only works with hibernate, meaning you can kiss good bye to jpa api's . (sure you wanna do that, think hard before you answer, then think harder) . now comes RequestFactory, yes, it has it's issues, including annoying amount of boilerplate code, but it does allow you to send and synchronize changes from client to server automatically, on the down side it forces you to create interfaces for the client side. which although smell like an old sock , it's better now since google were kind enough to include annotation processing in their GPE, (which alarms you of any missing mismatch of getter setter) another thing with RF, is that google is pushing it really hard, including development on android platform, and using it on the server side as well. so you should take that as a plus also. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/IQAtQn7QaOMJ. 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.
