Re: again with 'works in jetty, not in tomcat' for simple URI matching in 2.2

On 02/09/2011 04:00 PM, Myles Byrne wrote: Thanks, Andre! It would be a godsend to route around this problem. But I haven't been able to get param passing to work as you suggest. Following from your example, this sitemap match: map:pipeline map:match pattern=something map:match

Re: again with 'works in jetty, not in tomcat' for simple URI matching in 2.2

Andre, that's very helpful. You're right, the URL value is a remote server - plus it's HTTPS. What kills me is that it works fine with Jetty, but as soon as i build the webapp and move the WAR into Tomcat, it breaks. What causes Tomcat to evaluate a URI as a local filepath, while Jetty hits it

Re: again with 'works in jetty, not in tomcat' for simple URI matching in 2.2

Thanks, Andre! It would be a godsend to route around this problem. But I haven't been able to get param passing to work as you suggest. Following from your example, this sitemap match: map:pipeline map:match pattern=something map:match type=request-parameter pattern=url / map:generate

again with 'works in jetty, not in tomcat' for simple URI matching in 2.2

Hi all, Coming right off the current basic archetype with samples, simply adding a basic URL matcher: map:match pattern=url=** map:generate src={1}/ etc .. .. works fine in Jetty, but in Tomcat throws: Javax.servlet.ServletException: org.apache.cocoon.ProcessingException: Sitemap: error

URI matching.

I have browsed through the documentation and the mail lists, but so far I haven't found an answer for this problem. Let's say I have an URI that looks like this: http://www.domain.com/cocoon/knowledge/article?id=123 And a sitemap.xmap file that is located in the directory knowledge. Can I

RE: URI matching.

From: Ronald Borman [EMAIL PROTECTED] Date: Mon, 22 May 2006 23:22:18 +0200 I have browsed through the documentation and the mail lists, but so far I haven't found an answer for this problem. Let's say I have an URI that looks like this: