for some context on my request, first, and foremost, it sure is hard to find complete, and contemporary examples of the numerous open source advancements since the first, and seemingly only literature of gwt was rushed out in the 2007-2008 timeframe. there is 0 literature for purchase about gwt+gae/J, and almost as little about gae/j in general ; however, there are competing and confusing bands of mavenization efforts, all of which seem to lack a meaty CRUD archetype to close the gap on the repo choices and the lib/ inclusion choices. If I'm missing some modern publications, please clue me in! I have located fractions of real-world CRUD solutions in several [e]books, less from blogs, but using gae/j really adds bleeding to the process.
second, I'm a complete newcomer to gae/j and gwt altogether, basing estimates, and customer expectations on what can be considered anecdotal uncertainties, uncertain as to where i can borrow example solutions from at least. so the root of my request for this formula of buzzwords is: view: gwt: I am porting a swing (JNLP) kiosk client and sharing hopefully some super-user RPC or JSON CRUD events with a hosted application. part2 is replacing swing outright. model: appengine,xstream: I am looking to migrate said kiosk from a standalone OpenJPA/Derby Model to a split model of Local Appengine/Cloud-Appengine Datanucleus JPA to run the kiosk on mini-me appengine and the various super-usecases on the hosted appengine with some level of record transfer parsimony: maven,bigtable,jpa: migrating from derby embedded storage on JPA, to uniform, mavenized model package with syncronicity between kiosk and hosted super-CRUD usecases, for this purpose JDO is not out of the question, if it opens up the pool of examples to draw from. that's not a desired goal, since it involves retooling the persistence manager on the swing client in production. issues i am aware of involve prior to finalizing the gameplan is choosing a path of inter-app rpc a) JDO, b) JPA+DTO, or c) including the javax.persistence.* source code in the model layer, the latter sounding preferable. commentaries on experience here would be helpful. thanks for reading this far. Jim -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
