simon litwan wrote:
i think you're right, but one step after the other.
i really would like if this problem is a kind of fixed.
since the this directory, where the content-dir is pointing to, could
have more than just the content it would make sense to rename it later
on to something more appropriate.
but most important seems to me to resolve this inconsistency.
so i would propose to handle the absolute path like the relative.
comments are welcome.
if nobody else, i will comment my self ;)
the problem is caused in the method SourceNode.getRealSourceURI() where
you get on base of Publication.getContentDir() the real source uri back.
if the content-dir is not configured the method
Publication.getContentDir() gives back an absolute path with /content
at the end.
now if you configure the content-dir in publication.xconf as recommended
without /content at the end the method Publication.getContentDir() will
never give you back a /content.
since this issue actually is not connected to the rcml and what ever
files could be in the content directory as well (as it is now), i really
would change the recommendation and add a /content at the end of
content-dir .
<content-dir src="lenya/pubs/default/content"/>
<content-dir src="/home/USERNAME/data/default/content"/>
<content-dir src="D:/tmp/default/content"/>
+1
--
"Open source takes the bullshit out of software."
- Charles Ferguson on TechnologyReview.com
--
Jörn Nettingsmeier, EDV-Administrator
Institut für Politikwissenschaft
Universität Duisburg-Essen, Standort Duisburg
Mail: [EMAIL PROTECTED], Telefon: 0203/379-2736
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
