Daniel Fagerstrom wrote:
Vadim Gritsenko wrote:
Sylvain Wallez wrote:
Daniel Fagerstrom wrote:
The idea for blocks is that blocks that contain public URLs are
mounted at deploy time at a some root URL, then the URL revriting
transformer translates internal use of symbolic block names to the
public exported ones.
Why would anyone internally use any block: URIs? This should be
totally unnecessary: you can either use relative URIs,
You need to use block:foo: URIs to access resources in other blocks,
block: URIs to use URIs that you want polymorphic behaviour on, and
block:super: for geting an URI from the block that you extend. See
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=111791016006393&w=2 for
more details.
or construct absolute by passing sitemap prefix into the xslt - same
as we do in existing samples.
Using the LinkRewritingTransformer together with the block-path module
will be so much more convenient (see the cited mail above).
Hm, I found no sample where linkrewriter is necessary [1]. All I saw is usage of
block: protocol from the sitemap, which I understand. I just don't see there are
many (any?) usecases for the block: URIs in the pipelines. Either way I'm
thinking it will be relatively obsure usecase anyway.
Vadim
[1]
http://svn.apache.org/viewcvs.cgi/cocoon/trunk/src/test/org/apache/cocoon/components/blocks/?rev=189457
