Yup he should then let cocoon announce on his mailing list as well.
I'ld still prefer no announcements whatsoever though ...
-Original Message-
From: C Bram Dit Saint Amand [mailto:[EMAIL PROTECTED]
Sent: Dienstag, 22. Juli 2003 21:14
To: [EMAIL PROTECTED]
Subject: Re: [ANN] OXF 2.0
I have a Cocoon site which I'm trying to cache (with a reverse-proxy). To cache a
page, the proxy seems to require a Content-Length header, but some of my Cocoon
pipelines don't return this header. I don't know why - can anyone enlighten me? I'm
using c2.1m2
Cheers
Con
--
Conal Tuohy
Senior
On Sat, 2003-07-19 at 23:41, Eric Gulatee wrote:
Now basically my problem is that I want to be
able
to hook into my own validation routines on top of
Woody's. [If you're registering a user, you need
to
verify the name is available]... Now I've noticed
that if you hook into your own
Alexandre Victoor wrote:
Hello
I would like to know if it is possible to have a pipeline that can't be
accessed internally.
Don't think so - but why?? You trust external users from the internet
more than your own code?
I would like to be able to write something like that :
map:match
we have a "main"
pipeline which handles all requests by firstly performing authentication and
lastly performing internationalization, browser tweaking, etc. the middle
part of the pipeline is different per page so we wanted to organize things with
a subsitemap per page (easiest
Hello,
Im a newbie to Cocoon and am still trying to understand the framework.
I have installed and running, cocoon-2.1m3-dev.
I downloaded and installed a site called bonebreaker in c:\cocoon\build\webapp\samples so that i have something like this..c:\cocoon\build\webapp\samples\bonebreaker.
I
You may be able to use a referer matcher/selector to try to guarantee that
the request is really coming from outside. I fail to understand why you
need this. Maybe elaborating on that would help come up with better options.
Geoff
In my main pipeline I have something like that :
map:match
[EMAIL PROTECTED] wrote:
you might consider using Apache in front of Tomcat (connected for
instance by mod_proxy)
and serve the images from Apache instead through Cocoon.
Michael
is there any description of that configuration in the net?
I'd be thankful :-)
Hi Tony,
xsl:template name=createOptionList
xsl:param name=parentNode select=string() /
xsl:param name=childNode select=string() /
xsl:variable
name=targetNode
select=concat(name($listNode),'/',$listItem) /
xsl:for-each select=$targetNode
... do
Well, if you have your xpath in $targetnode, wouldn't it simply be:
xsl:apply-templates select=$targetnode/?
or
xsl:for-each select=$targetnode
xsl:apply-templates/
/xsl:for-each
To go along with your code. I haven't done XSLT in a while, so I'm a
little rusty.
Hi
Adam there's no dynamic xpath expression evaluation in XSLT - you'll probably want
to find some other way to identify the nodes you want to deal with since writing a
generic xpath evaluator in XSLT is not going to be easy. It would be feasible though
to parse some standard type of expressions
--- Conal Tuohy [EMAIL PROTECTED] wrote:
Adam there's no dynamic xpath expression evaluation in XSLT - you'll
probably want to find some other way to identify the nodes you want to deal
with since writing a generic xpath evaluator in XSLT is not going to be easy.
It would be feasible though to
Alessio Sangalli wrote:
Joerg Heinicke wrote:
What was your JDK and Cocoon version with the last install?
the last install? I wrote all the versions I've used this time:
Hmm, ok. Many people only update the current install and have then a
problem with the compatibility of the XML libraries.
Hi Adam,
Have you tried using name() function like:
xsl:apply-templates
select=/*[name()=$parentNode]/*[name()=$childNode]/
However, as far as I know name() function is there for
emergency cases, rather than normal usage.
If you know what the nodes might be, you might want to
use several
map:mount seems to be ok. For me the url of the subsitemap seemed to be
wrong:
cocoon_vdab18653.war!/sitemap.xmapextractie/algemeen/sitemap.xmap. It
looks like a path resolving bug to me. We know of different ones of them
already (see bugzilla for them). The path resolving is too much
Hello Adam,
My apologies for the lack of clarity. I was trying to use the value I have
calcualted for the $targetNode variable to select a node in my XML document.
If I had an xml source like the following, I would like to be able to
'dynamically' select nodes for processing.
...
The xslt
Have you tried using name() function like:
xsl:apply-templates
select=/*[name()=$parentNode]/*[name()=$childNode]/
However, as far as I know name() function is there for
emergency cases, rather than normal usage.
If you know what the nodes might be, you might want to
use several
Hi Adam,
I don't think select=$parentNode/ will work. You
cannot use variables in place of element names.
Alex
--- Adam Flegman [EMAIL PROTECTED] wrote:
Have you tried using name() function like:
xsl:apply-templates
select=/*[name()=$parentNode]/*[name()=$childNode]/
However, as
NB to avoid problems namespaces you might want to use the local-name() function
instead of the name() function.
e.g.
if $parent=foo and $child=bar then:
/*[local-name()=$parent][*[local-name()=$child]]
should return all nodes which match the xpath /foo/bar
Cheers
Con
-Original
19 matches
Mail list logo
