On 30 Nov 2003, at 21:41, Ryan Hoegg wrote:
Stefano Mazzocchi wrote:
I think a much better approach would be to come up with a
Repository.java
interface and a few implementations that I can choose when I install cocoon. This implementation would also implement Source.java and provide its functionality thru a URL protocol.
This allows:
- clear separation of concerns: cocoon should *NOT* be doing repository stuff, which is already big and complex enough
- complete IoC: you choose the implementation and the implementation decides what to do and how to do it. Your contract remains the same (thru the source-provided URL protocol and thru the component interface)
- transparent polymorphism: you can have different implementations of a repository... file system, webdav, CVS, JCR, ... without having to change any code in your application
Thoughts?
-- Stefano.
Looks good! However, I think some people may not need all 5 of your requirements:
Great, don't use them.
> Functionality I need is: > > 1) open/save document > 2) create collection of documents
I think these are the core requirements of a repository.
oh, c'mon, that's a core requirement of a file system and you already have it.
I also think a simple form of document retrieval (like a Source) is necessary, but that might just be rolled into "open"
And you have that as well, it's called "file:"
> 3) attach metadata to documents (externally to them!!) > 4) query the repository against document metadata > 5) versioning (autoversioning on saving and version update)
Some people might like to get versioning and metadata a la carte.
if so, don't use the repository and use the FS. but I don't get why you would want to do your own stuff once you have a library that does it for you.
Not all versioned repositories need an external metadata facility or the ability to query it. I think all versioned repositories do need some metadata (commit logs, permissions, etc).
So what about a basic Repository interface, a specialization of it for metadata, and a specialization of that for versioning?
I don't see the point in doing this. A repository without metadata and versioning is a file system and you already have an API to use that in java.io.*
-- Stefano.
smime.p7s
Description: S/MIME cryptographic signature
