was Re:
StackOverflowError in 2.1)
Ralph Goers schrieb:
Giacomo Pati wrote:
You mean the new WildcardMatcher is not behaving correctly? Any
TestCase to fix it? Is a match="menu/*" catching a uri="foo.html"?
No. match="*.html" is matching on "menu/index.htm
wErrors (was Re:
StackOverflowError in 2.1)
Giacomo Pati wrote:
>
> You mean the new WildcardMatcher is not behaving correctly? Any TestCase
> to fix it? Is a match="menu/*" catching a uri="foo.html"?
No. match="*.html" is matching on "me
Ralph Goers wrote:
> Carsten Ziegeler wrote:
>> Ralph Goers schrieb:
>>
>>> Were there test cases for the old wildcard matcher? Since this
>>> matcher is almost certainly used in every Cocoon deployment we must
>>> guarantee that it is 100% compatible with the old matcher in
>>> BRANCH_2_1_X - u
Ralph Goers wrote:
>>
> OK. But my question is really that if the old code didn't have unit
> tests how do we know that the new unit tests are compatible with the old
> matcher (i.e - that they get the same results)?
:) We added the old tests to the new test case and we added many test
cases
Carsten Ziegeler wrote:
Ralph Goers schrieb:
Were there test cases for the old wildcard matcher? Since this matcher
is almost certainly used in every Cocoon deployment we must guarantee
that it is 100% compatible with the old matcher in BRANCH_2_1_X -
unless, of course, there was some spec
Ralph Goers schrieb:
> Giacomo Pati wrote:
>> You mean the new WildcardMatcher is not behaving correctly? Any
>> TestCase to fix it? Is a match="menu/*" catching a uri="foo.html"?
> No. match="*.html" is matching on "menu/index.html".
>> I have to check that.
>>
>> Ciao
>>
>> Giacomo
> Were there
Ralph Goers schrieb:
> 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 *.
Giacomo Pati wrote:
You mean the new WildcardMatcher is not behaving correctly? Any
TestCase to fix it? Is a match="menu/*" catching a uri="foo.html"?
No. match="*.html" is matching on "menu/index.html".
I have to check that.
Ciao
Giacomo
Were there test cases for the old wildcard matcher?
Errors (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
&
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
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 s
11 matches
Mail list logo
