Hi Anamaria, On 01/05/2010 04:50 PM, Anamaria Stoica wrote: In xwiki, when you do getDocument(String docName) you will get a document even if the document does not exist, you'll get a new one. You can test this by checking XWikiDocument#isNew(). So, normally it will create a new document if you do DocumentAccessBridge#getDocument(documentName); however it should not be saved until a saveDocument() is called on that document. The way to do this with the bridge is to set values for the properties of that document or objects in it and it will be saved. There is no explicit saveDocument in the bridge because every operation on the bridge should be 'atomic', no operations should leave things changed and not persisted. I don't really like the approach I just described, because it's very hacky, and you won't be able to set all the properties you need anyway, you'll need to add a bunch of functions to the bridge. What you can do to make things easier for you, is to isolate all the code that needs to handle storage (creating documents, objects or others) to a single service in your code, and make only the implementation of that service depend on the old core. This way, when the refactoring will all be done, you only need to change your storage related impl and you're done. Happy coding, Anca