Hi Steve, Thanks for your interest in Apache Isis. This is definitely do-able, and is not actually that far removed from one of Isis' original goals, to have pluggable support for its components.
In fact, there is an Isis XML objectstore - though not yet formally released - which you could use as a starting point. It works by saving separate files in a folder, but I imagine it'd be easy to fork it and write it so that it stores all the files in a single big XML file. As an alternative (and, actually, one I'd recommend instead), you could use the JDO/DataNucleus objectstore, but then exploit DataNucleus's own pluggable DataStore API. There are a number of implementations; not just RDBMS, as you can see here [1]. And there is one that persists to XML [2], so you could explore that. I don't know how many people are actually using this DataNucleus API, but it is at least implemented and supported, so probably is a lower risk approach than rolling your own based on the Isis API. Let us know which approach you decide to take; happy to support you if possible. Cheers Dan PS: this enquiry probably lives better on the [email protected] list. [1] http://www.datanucleus.org/extensions/store_manager.html [2] http://www.datanucleus.org/products/datanucleus/datastores/xml.html On 20 May 2013 05:40, Stephen Cameron <[email protected]> wrote: > Hi > > I am starting a project looking at how best to auto-generate a simple data > gathering application. > > I'd like to drive it off an XML Schema document, I've made something > reasonably good for a web interface using XForms and soon an XML database > as a back-end, the so-called 'XRX architecture'. > > I've been reading the Naked Objects books and am interested to see what I > can do in a similar way with Apache ISIS, both for the ISIS web and native > Java viewers. > > One question I have is: can I make use of an XML database as the > persistence layer easily? The idea here being that the application > generates one big XML file, or an archive with multiple files, at the end > of a period, and that gets submitted to a central XML database. > > I guess that the history of ISIS would suggest that this is a strange thing > to do, as opposed to using a relational database. However, the method in my > madness is that I'm effectively building a no-code solution, asI'm hoping > all the ISIS java code can be generated. > > Thanks for your feedback > > Regards > Steve Cameron >
