-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sun, 9 Jul 2006, Ralph Goers wrote:
Date: Sun, 09 Jul 2006 23:26:08 -0700
From: Ralph Goers <[EMAIL PROTECTED]>
Reply-To: [email protected], [EMAIL PROTECTED]
To: [email protected]
Subject: Wildcard matcher causes StackOverflowErrors (was Re:
StackOverflowError in 2.1)
Well, I found the source of the problem. In the sitemap the matcher for
"*.html" was before the matcher for "menu/*". The matcher for "*.html" calls
the "composite" resource which in turn does a map:part for
"cocoon:/menu/{../1}.html". This is apparently matching *.html and causing
an infinite loop. Simply moving the *.html matcher after the menu/* matcher
causes the problem to go away.
In short, unless the new wildcard matcher is 100% compatible with the old one
it needs to be reverted in BRANCH_2_1_X.
You mean the new WildcardMatcher is not behaving correctly? Any TestCase
to fix it? Is a match="menu/*" catching a uri="foo.html"?
I have to check that.
Ciao
Giacomo
Ralph
Ralph Goers wrote:
I wanted to mess around with some of the input modules so I brought up the
input module page in the sample site. However, it dies with a
StackOverflowError. I then checked out the latest to another one of my
computers (with Linux instead of Windows) and got the same error.
Unfortunately, no stack trace is presented. I've tried going directly to
some of the samples on that page and can't get anything to work.
Ralph
- --
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (GNU/Linux)
iD8DBQFEsfzdLNdJvZjjVZARAtj7AJ4k7VoVDr0WFsBnLnXTujWG3y8lMACglX40
Ec0R5r1YCjaOIDTjPstZmQg=
=cUAq
-----END PGP SIGNATURE-----
