On 9 September 2012 15:01, Minto van der Sluis <[email protected]> wrote: > Thanks for al the responses regarding JDO vs SQL. > > However, my project moved in a direction where the model is not known at > compile time. So we need a solution capable of handling the model at > runtime. I am not sure if there still is a place for Isis in this scenario. >
That definitely rules out using one of the current objectstores, and indeed most of Isis' runtime infrastructure. With a little inside knowledge, I think it would be possible to use the core (metamodel) and the viewers, however. You would need to implement a number of FacetFactory's in order to build the metamodel from, well, wherever the information is. And you'd need to provide the backend runtime also, wrapped up in a form that Isis can access (ie through the IsisContext service locator). > > Currently I am thinking about modelling the domain in OWL and store the > data in a RDF database. Metawidget comes to mind for constructing a Gui > at runtime. > That may well be a good approach. You'll find that to use Metawidget you'll also need to implement its MetaModelBuilder API, and of course with MetaWidget you do all the backend runtime/persistence yourself anyway. My suggestion would be that you figure out your runtime/backend, using a very simple UI (to the console, even). Once you understand that, then you'll be in a better position to decide which framework (if either) to go with. Cheers Dan > > Regards, > > Minto > >
