Hi Augustinus, Have you considered using Isis using a lightweight data store.
For example, configuring the JDO Objectstore to use an in-memory HSQLDB connection just like the ToDo Archetype[1]. You could then create services that makes the calls to your webservices to read data into and send updates from your database. You can do this two ways: 1. Have explicit load and save operations. 2, Hook into the life cycle call backs [2] This approach is particularly useful when you have complex objects that you want to allow the user to build up before committing them to the web services. Regards, Ged [1] http://isis.apache.org/intro/getting-started/todoapp-archetype.html [2] http://isis.apache.org/reference/object-lifecycle-callbacks.html On 10 October 2014 08:48, <[email protected]> wrote: > I'd like to use ISIS for my Web-App (.war / Tomcat) but I don't need all > the persistence stuff > cause I have to call a WebService instead of that. > > My idea: > > - Compile wsdl2java (using jdk wsimport now) > - Enrich (merge in) the generated .java files with the > ViewModel-methods (deriving the classes from ViewModel) > - Build services calling the webservice > > My questions: > > - Is that idea a good one or should I go some other way ? > - Is anybody out there who did that already willing to share some > experiences ? > > Basically I'd like to get all of ISIS but no persistence > cause I have very deep data-structures to be shown and edited in the UI > which I don't want to build up by means of Vaadin > > Any help or just little hints appreciated! > (Even "That's a stupid idea remarks" :-) ) > > Augustinus Deimel > >
