Hi Andrew, Gosh, that's going back a long way!
Yes, there did used to be an XML object store, but we removed it many years ago once we had the JDO/DataNucleus object store going. The reason is that DataNucleus has its own SPI [1] to allow different persistence mechanisms to be plugged in, namely StoreManager. As [2]'s DataStore menu shows, it supports not only RDBMS but a number of other NoSQL objectstores (Neo4J, Cassandra, MongoDB). I see there is also an XML object store for JAXB-annotated classes [3]. Although most everyone in the user community uses RDBMS, there was someone who set up Neo4J; we built an example app [4] to demo it (currently broken mind). They got that working with not too much jiggery-pokery. So hopefully the same would be true for using the XML store. Hope that helps. Dan [1] http://www.datanucleus.org/documentation/extensions/store_manager.html [2] http://www.datanucleus.org/products/accessplatform_4_1/index.html [3] http://www.datanucleus.org/products/accessplatform_4_1/datastores/xml.html [4] https://github.com/isisaddons/isis-app-neoapp On 12 April 2016 at 06:33, Andrew Voumard <[email protected]> wrote: > Hi, > > I believe an earlier version of the framework supported storing entities > as JAXB marshalled XML (presumably in ordinary files on disk). I have a > data model which contains approx 15 entity classes, with a typical quantity > of associations and constraints amongst them. The model instances are > stored as JAXB marshalled XML files, and are hand edited. I was thinking of > using this framework to provide a simple UI to create/edit instances of the > data model, but wanted to keep the data store as JAXB marshalled XML files > if that is possible. Would that be possible with the current framework > implementation ? > > Thanks > Andrew >
