|
| Re: [CDO] folder concept [message #720270 is a reply to message #720265] |
Tue, 30 August 2011 09:18  |
|
Am 30.08.2011 11:11, schrieb exquisitus:
> Hi, I have a general question to the CDOResourceFolder.
> Namely I designed my own folder metamodel (instances contained in a CDOResource) but always thought of
> using the existing CDOResourceFolder instead. So anybody knows which way to go in general?
Both is possible.
> Has CDOResourceFolder any build-in advantages?
Perhaps that they're more easily queriable, see:
org.eclipse.emf.cdo.view.CDOView.queryResources(CDOResourceFolder, String, boolean)
org.eclipse.emf.cdo.view.CDOView.queryResourcesAsync(CDOResourceFolder, String, boolean)
> Or maybe disadvantages (not being contained in a CDOResource, and thereby not being able to edit in EMF editors)?
Technically everything is contained by a resource. In CDO there's the special root resource that contains the top-level
CDOResourceNodes (CDOResources and CDOResourceFolders).
CDOResourceNodes are EObjects and can be manipulated like all other EObjects.
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
>
> I make the folder structure accessible by WebDav. The user can upload/download files in the folders, being mapped to
> Blobs and/or EMF models in the CDO database. As this is quite generic functionality, I will try to open-source this.
> Still thinking about how to integrate existing resource implementations into this architecture. Architectural models
> are my domain, which are by nature very large, so I also want to support resume of upload/download of models, where
> EMF does not help much with concepts. Just thinking, any ideas welcome..
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
Powered by
FUDForum. Page generated in 0.02964 seconds
] 
Search
Help
Register
Login
Home
