You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lenya.apache.org by Thorsten Scherler <th...@wyona.com> on 2006/03/08 11:22:23 UTC
Re: svn commit: r383910 - in
/lenya/trunk/src/modules/opendocument:config/cocoon-xconf/
config/menus/ java/ java/src/ java/src/org/java/src/org/apache/
java/src/org/apache/lenya/java/src/org/apache/lenya/cms/
java/src/org/apache/lenya/cms/site/java/src...
El mié, 08-03-2006 a las 00:42 +0100, Michael Wechner escribió:
> Thorsten Scherler wrote:
>
> >El mar, 07-03-2006 a las 17:00 +0100, Thorsten Scherler escribió:
> >
> >
> >>El mar, 07-03-2006 a las 16:49 +0100, Andreas Hartmann escribió:
> >>
> >>
> >>>>+ String urlID = "content/" + document.getArea() + document.getId()
> >>>>+ + "/" + DEFAULT_INDEX + "_"
> >>>>+ + document.getLanguage() + ODT_EXTENSION;
> >>>>
> >>>>
> >>>:(
> >>>
> >>>This code will break with a custom DocumentIdToPathMapper.
> >>>
> >>>
> >>Yeah, I know. :(
> >>
> >>
> >
> >BTW that is not the only part of this module. Like I said in the other
> >thread you can find in lenya-trunk/src/modules/opendocument/sitemap.xmap
> > <map:generate
> >src="zip:context://lenya/pubs/{page-envelope:publication-id}/content/{page-envelope:area}/{page-envelope:document-id}/index_{page-envelope:document-language}.odt!/content.xml"/>
> >
> >You are right, that does not make the above code better but since the
> >usages is already limited I just used this knowledge. ;)
> >
> >
>
> btw, you might just want to improve the line above by using the lenya
> protocol, etc. ;-)
Well http://lenya.apache.org/1_4/reference/protocols/lenya.html
"The resolution of the URI is based on the context: protocol handler."
so not an option.
lenya-doc http://lenya.apache.org/1_4/reference/protocols/lenyadoc.html
is assuming file extension xml as far as I understand it ATM, so not an
option.
One could extend the above protocols though (I think best would be the
lenya-doc). The only protocol that I made aware of the content-dir is
the fallback:// but it feels like an abuse to use it to get content.
Further it does not solve the "custom DocumentIdToPathMapper" problem.
I will have a closer look now on the lenya-doc.
salu2
--
Thorsten Scherler
COO Spain
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
thorsten.scherler@wyona.com thorsten@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: svn commit: r383910 - in /lenya/trunk/src/modules/opendocument:config/cocoon-xconf/
config/menus/ java/ java/src/ java/src/org/java/src/org/apache/ java/src/org/apache/lenya/java/src/org/apache/lenya/cms/
java/src/org/apache/lenya/cms/site/java/src...
Posted by Andreas Hartmann <an...@apache.org>.
Thorsten Scherler wrote:
> El jue, 09-03-2006 a las 09:58 +0100, Andreas Hartmann escribió:
>> Thorsten Scherler wrote:
>>
>> [...]
>>
>>>> btw, you might just want to improve the line above by using the lenya
>>>> protocol, etc. ;-)
>>> Well http://lenya.apache.org/1_4/reference/protocols/lenya.html
>>> "The resolution of the URI is based on the context: protocol handler."
>>> so not an option.
>> That's not the whole story. The lenya:// protocol just points to respository
>> nodes. Whether the nodes use context:// sources, or JCR nodes, or whatever,
>> depends on the NodeFactory you use.
>>
>
> Does that mean that I can get with
> Node node = getRepositoryNode(destination);
> node.lock();
> any given destination uri?
I don't quite understand what you mean with "destination URI" ...
You can access all nodes which are provided by the NodeFactory.
[...]
>>> Further it does not solve the "custom DocumentIdToPathMapper" problem.
>> Yes, which is the root of all evil in this issue. We have to solve it,
>> then the problems will vanish.
>
> Ok, then we should start the meta data stuff.
+1
-- Andreas
--
Andreas Hartmann
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
andreas.hartmann@wyona.com andreas@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: svn commit: r383910 - in
/lenya/trunk/src/modules/opendocument:config/cocoon-xconf/ config/menus/
java/ java/src/ java/src/org/java/src/org/apache/
java/src/org/apache/lenya/java/src/org/apache/lenya/cms/
java/src/org/apache/lenya/cms/site/java/src...
Posted by Thorsten Scherler <th...@apache.org>.
El jue, 09-03-2006 a las 09:58 +0100, Andreas Hartmann escribió:
> Thorsten Scherler wrote:
>
> [...]
>
> >> btw, you might just want to improve the line above by using the lenya
> >> protocol, etc. ;-)
> >
> > Well http://lenya.apache.org/1_4/reference/protocols/lenya.html
> > "The resolution of the URI is based on the context: protocol handler."
> > so not an option.
>
> That's not the whole story. The lenya:// protocol just points to respository
> nodes. Whether the nodes use context:// sources, or JCR nodes, or whatever,
> depends on the NodeFactory you use.
>
Does that mean that I can get with
Node node = getRepositoryNode(destination);
node.lock();
any given destination uri?
>
> > lenya-doc http://lenya.apache.org/1_4/reference/protocols/lenyadoc.html
> > is assuming file extension xml as far as I understand it ATM, so not an
> > option.
>
> That's only because the DocumentIdToPathMapper is tied to the publication
> and not to the resource type. We have already discussed that.
ok
>
> > One could extend the above protocols though (I think best would be the
> > lenya-doc). The only protocol that I made aware of the content-dir is
> > the fallback:// but it feels like an abuse to use it to get content.
>
> This is true. Please don't use it!
;)
> > Further it does not solve the "custom DocumentIdToPathMapper" problem.
>
> Yes, which is the root of all evil in this issue. We have to solve it,
> then the problems will vanish.
Ok, then we should start the meta data stuff.
> -- Andreas
>
Thanks for your feedback. :)
salu2
--
thorsten
"Together we stand, divided we fall!"
Hey you (Pink Floyd)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: svn commit: r383910 - in /lenya/trunk/src/modules/opendocument:config/cocoon-xconf/
config/menus/ java/ java/src/ java/src/org/java/src/org/apache/ java/src/org/apache/lenya/java/src/org/apache/lenya/cms/
java/src/org/apache/lenya/cms/site/java/src...
Posted by Andreas Hartmann <an...@apache.org>.
Thorsten Scherler wrote:
[...]
>> btw, you might just want to improve the line above by using the lenya
>> protocol, etc. ;-)
>
> Well http://lenya.apache.org/1_4/reference/protocols/lenya.html
> "The resolution of the URI is based on the context: protocol handler."
> so not an option.
That's not the whole story. The lenya:// protocol just points to respository
nodes. Whether the nodes use context:// sources, or JCR nodes, or whatever,
depends on the NodeFactory you use.
> lenya-doc http://lenya.apache.org/1_4/reference/protocols/lenyadoc.html
> is assuming file extension xml as far as I understand it ATM, so not an
> option.
That's only because the DocumentIdToPathMapper is tied to the publication
and not to the resource type. We have already discussed that.
> One could extend the above protocols though (I think best would be the
> lenya-doc). The only protocol that I made aware of the content-dir is
> the fallback:// but it feels like an abuse to use it to get content.
This is true. Please don't use it!
> Further it does not solve the "custom DocumentIdToPathMapper" problem.
Yes, which is the root of all evil in this issue. We have to solve it,
then the problems will vanish.
-- Andreas
--
Andreas Hartmann
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
andreas.hartmann@wyona.com andreas@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org