Hi,
I have a pipline that generates a file in the filesystem using a generator
and a transformation. The output is empty but I want to present in the
same request one of the generated files (index.html).
I tried to use
map:generate src=.../
map:transform type=xslt src=.../
map:redirect-to
Peter Klotz wrote:
So how can one read a file from the filesystem after a transformation?
You can write a transformer / serializer that reads a file and
generates the appropriate SAX events. I don't know if such a
component already exists.
And why does the redirect not work?
There are some
Andreas Hartmann wrote:
Peter Klotz wrote:
So how can one read a file from the filesystem after a transformation?
You can write a transformer / serializer that reads a file and
generates the appropriate SAX events. I don't know if such a
component already exists.
Maybe you could use a
At 10:00 AM 6/3/2003, you wrote:
...
map:generate src=.../
map:transform type=xslt src=.../
map:redirect-to uri=chunk_{1}/
map:redirect-to issues a client side redirect. under what
circumstances would you want to do that along with an pipeline
content? are you looking for something like
At 10:31 AM 6/3/2003, you wrote:
Andreas Hartmann wrote:
Peter Klotz wrote:
So how can one read a file from the filesystem after a transformation?
You can write a transformer / serializer that reads a file and
generates the appropriate SAX events. I don't know if such a
component already exists.
Geoff Howard wrote:
[...]
xsl:template match=/
xsl:copy-of select=document($source)/*/
/xsl:template
I think that should work.
It may, but I'd not recommend it.
Agreed. I should have mentioned this :)
Andreas
-
To
--- Geoff Howard [EMAIL PROTECTED] wrote:
At 10:00 AM 6/3/2003, you wrote:
...
map:generate src=.../
map:transform type=xslt src=.../
map:redirect-to uri=chunk_{1}/
map:redirect-to issues a client side redirect.
under what
circumstances would you want to do that along with
an pipeline
map:call transfers to a pipeline fragment defined in
map:resources, but I don't think it will help you
specifically now that I see what you are trying to
do.
How about using an xslt transform after the
SourceWritingTransformer with something that
completely replaces all nodes with a cinclude?
eg,
map:call transfers to a pipeline fragment defined in
map:resources, but I don't think it will help you
specifically now that I see what you are trying to
do.
map:call does not work the same way as map:redirect-to does not work
because the steps before are not executed. Both must be the first
map:call does not work the same way as map:redirect-to does not work
because the steps before are not executed. Both must be the first and only
statements in a map:match.
Hello Peter,
fortunately the above is not true ;-)
map:call resource=resourcename/ is a sitemap internal redirect for
At 01:03 PM 6/3/2003, you wrote:
so you'd do
...
map:transform type=write-source/
map:transform src=that.xsl/
map:transform type=cinclude/
...
I know both xinclude (and cinclude) as well as xsl:document() should work,
the problem is that the file to include is a relative URL to the
--- Geoff Howard [EMAIL PROTECTED] wrote:
At 01:03 PM 6/3/2003, you wrote:
so you'd do
...
map:transform type=write-source/
map:transform src=that.xsl/
map:transform type=cinclude/
...
I know both xinclude (and cinclude) as well as
xsl:document() should work,
the problem
Ok, how about sending them a page with a meta refresh tag?
I think an elegant solution exists with flow in 2.1, but
couldn't help you get there at this stage.
Geoff
-Original Message-
From: Alex Romayev [mailto:[EMAIL PROTECTED]
--- Geoff Howard [EMAIL PROTECTED] wrote:
At 01:03
Hi Joerg,
map:call does not work the same way as map:redirect-to does not work
because the steps before are not executed. Both must be the first and
only
statements in a map:match.
[...]
fortunately the above is not true ;-)
map:call resource=resourcename/ is a sitemap internal redirect
Hello Peter,
Peter Klotz wrote:
map:call resource=resourcename/ is a sitemap internal redirect for
reusing pipeline fragments and so you can do first steps of a pipeline on
another place than the resource.
See also map:resource/.
I hear you saying this but when I try this
map:resources
15 matches
Mail list logo
