Michael Wechner wrote:
Andreas Hartmann wrote:
[...]
- the resource type can be asked for the path to read the document from
(or maybe it is sufficient to ask the resource type for the
file extension)
I dunno understand, can you explain a bit more.
We have a circular dependency:
- The resource type is stored in the meta data.
- The location of the meta data is determined by the DocIdToPathMapper.
- The DocIdToPathMapper should be determined by the resource type.
That's why we have to break a dependency. The easiest one
to break is the dependency from the meta data location to
the DocIdToPathMapper. We could use a generic location for
meta files, without using the mapper. Just something like
{document-id}.{language}.meta
why not have something like
.lenya/meta/{document-id}
whereas the ".lenya" would be configurable?
(this path could also be used within a JCR repo)
Just FYI: The JCRSourceNode uses JCR properties to store the
meta data, so no special path is needed.
-- Andreas
--
Andreas Hartmann
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
[EMAIL PROTECTED] [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
