Thorsten Scherler wrote:
El vie, 10-03-2006 a las 13:13 +0100, Andreas Hartmann escribió:
Thorsten Scherler wrote:
[...]
...
@@ -331,7 +346,9 @@
RepositorySource source = null;
try {
resolver = (SourceResolver)
this.manager.lookup(SourceResolver.ROLE);
- source = (RepositorySource)
resolver.resolveURI(getSourceURI());
+ String sourceUri = getPublication().getSourceURI() +
"/content/" + getArea()
+ + getId() + "/index_" + getLanguage() + ".xml";
+ source = (RepositorySource) resolver.resolveURI(sourceUri);
this.metaDataManager = source.getNode().getMetaDataManager();
} catch (Exception e) {
throw new RuntimeException(e);
This code change is not compatible with custom mapping.
It is compatible. You just have to move your meta files once.
¿?
The above string is looking up:
lenya://lenya/pubs/myPub/content/authoring/index/index_en.xml
Yeah, to move the meta to
lenya://lenya/pubs/myPub/content/authoring/index/index_en.xml.meta but
that does make 0% sense for custom mapping if I want this location I
would not write a custom mapper.
The hard-coded location applies only to the meta sources.
The location of the actual document sources is determined by
your custom DocumentIdToPathMapper.
We need to change this ASAP. I recommend to create a meta data dir (like
mentioned from others as well) and get the metada from there.
This is fine with me. I just used the behavior of the
DefaultDocumentIdToPathMapper for the moment so that most people don't
have to migrate their meta files to a new location.
We need use the Mapper to lookup the sourceURI.
No, you can't use the mapper, because the mapper has to access the
document source extension. But this would require access to the meta
data. You'll end up with a StackOverflowError. I already mentioned
this problem a couple of times.
Yeah, I just found out myself. ;)
:)
-- 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]
