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 pro
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:
.. would require this matcher setup in components,
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:
.. would require this matcher setup in components, no?
I haven't been able to get
On 02/08/2011 04:32 PM, Myles Byrne wrote:
Hi all,
Coming right off the current basic archetype with samples, simply adding
a basic URL matcher:
You could rewrite this as
This should work fine with a request like:
www.foo.com/something?url=value
etc ..
..
Hi all,
Coming right off the current basic archetype with samples, simply adding a
basic URL matcher:
etc ..
.. works fine in Jetty, but in Tomcat throws:
"Javax.servlet.ServletException: org.apache.cocoon.ProcessingException:
Sitemap: error invoking matcher" (the rest of the trace is b
