|Re: [CDO] MemStore with file-based backend [message #1471429 is a reply to message #1463475]
||Thu, 13 November 2014 04:31
|| Eike Stepper
Registered: July 2009
Am 06.11.2014 um 16:52 schrieb Stephane Fournier:|
> Indeed, my need was not cristal clear :)
> Hence, my needs are both :
> 1) make a dump of a MemStore as files (XML content would be perfect as EMF serialisation does,) every XX minutes. I
> found out CDOCommandProvider that provides an ExportCommand, but I don't know how to call it from CDO views ? Is it
> possible ?
The server-side entry point is org.eclipse.emf.cdo.server.CDOServerExporter.exportRepository(OutputStream). You can see
that it's only called by the CDOCommandProvider, but you could
1) Implement your own client/server protocol (e.g. with Net4j) to trigger a CDOServerExporter from a client.
2) Implement a CDORemoteSessionMessage-based protocol between a client and a server-embedded client to do the same.
3) Use telnet or something to gain access to the server console and use the shipped CDOCommandProvider.
> Do you have an example how to use this command ?
No, but syntax help is displayed on the console.
> 2) on commits, dump only the modified resources. Indeed, my model is split in many CDOResources (according to initial
> XmlResources) to minimize the number of resources to serialize as XML files.
This could be comparingly simple if you make use of the newer IRepository.Props.SERIALIZE_COMMITS option/feature. Could
be a nice contribution to CDO ;-)
Powered by FUDForum
. Page generated in 0.01982 seconds