Dear all,
Cocoon-3 ordinary pipeline components offer a flexible way to organise
REST-full calls between services.
(REST, after all is a principle, not a framework).
However, curiosity drove me into setting up a small example of a JAX-RS
webservice.
1. with mvn jetty:run : works perfectly
2. as a
On 05/17/2012 07:32 PM, Bob Harrod wrote:
We've recently upgraded our Cocoon 2.1 based web app from Tomcat 4 to
Tomcat 6. Our sitemaps were written with a somewhat invalid matchers
which worked in Tomcat 4:
For example:
...
Tomcat 6 more adequately adheres to the HTTP URL spec and append
We've recently upgraded our Cocoon 2.1 based web app from Tomcat 4 to
Tomcat 6. Our sitemaps were written with a somewhat invalid matchers which
worked in Tomcat 4:
For example:
...
Tomcat 6 more adequately adheres to the HTTP URL spec and appends a
trailing slash. Of course, the trailing s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andy,
On 5/16/12 12:36 PM, Andy Stevens wrote:
> Hi Bob,
>
> Assuming you have the request input module in your cocoon.xconf,
> then you can pass the context path into an xsl:param (or otherwise
> use in the sitemap) with e.g. src="mytransform.xslt"
Including {request.contextPath} as a transform param did the trick, thanks!
Is there any way to do this globally for all matches in the sitemap or does
it have to be passed to each transform?
- Bob
On May 16, 2012 12:53 PM, "Bob Harrod" wrote:
> Ok, thank you! I can look at the LinkRewriterTra
