Eddie and others - that change did the trick. I'm now back in business
with Cactus tests! Many thanks. I'll keep the issue open with the
Cactus folks and I very well could be doing something strange in my test
case configuration as well, but at least Struts is still happy and now
I'm happy!
I'm still not having any luck with this issue (now at the 20021029
build). I've been toying with the request.setURL call in a Cactus
beginXXX method, but that has no effect at all on this even though I can
tell my setting of the servlet path is working (in my testXXX I println
Erik Hatcher wrote:
I'm still not having any luck with this issue (now at the 20021029
build). I've been toying with the request.setURL call in a Cactus
beginXXX method, but that has no effect at all on this even though I
can tell my setting of the servlet path is working (in my testXXX I
I decided to try out a Struts nightly build (from a previous 1.1beta2
version) and I ran our Cactus test suite to see if all validated ok...
but I'm getting all Struts tests failing with this error:
String index out of range: -1
java.lang.StringIndexOutOfBoundsException: String index out of
Oh, sorry for omitting this nightly build 20021028 is the one I
tried and got the errors below
Erik Hatcher wrote:
I decided to try out a Struts nightly build (from a previous 1.1beta2
version) and I ran our Cactus test suite to see if all validated ok...
but I'm getting all Struts
More information after digging a bit. The change to RequestUtils (in
version 1.61) has this log:
Revision : 1.61
Date : 2002/10/15 17:37:25
Author : 'ekbush'
State : 'Exp'
Lines : +33 -11
Description :
Change RequestUtils.selectApplication so that it looks for an exact
match
rather than using
Can you verify your assumption with the logging output? It should say
what the value of matchPath is. This would be a debug-level logging
statment indicated by a line stating:
Selecting module for path matchPath
You may have to turn up the volume on your logging output to see it.
I'd be
Eddie Bush wrote:
Can you verify your assumption with the logging output? It should say
what the value of matchPath is. This would be a debug-level logging
statment indicated by a line stating:
Selecting module for path matchPath
You may have to turn up the volume on your logging output to
On Mon, 28 Oct 2002, Erik Hatcher wrote:
Date: Mon, 28 Oct 2002 13:42:44 -0600
From: Erik Hatcher [EMAIL PROTECTED]
Reply-To: Struts Developers List [EMAIL PROTECTED]
To: Struts Developers List [EMAIL PROTECTED]
Subject: Re: Nightly build issue
Eddie Bush wrote:
Can you verify your
[mailto:jakarta-struts;ehatchersolutions.com]
Sent: Monday, October 28, 2002 19:43
To: Struts Developers List
Subject: Re: Nightly build issue
Eddie Bush wrote:
Can you verify your assumption with the logging output? It should say
what the value of matchPath is. This would be a debug-level logging
Eddie Bush wrote:
Can you verify your assumption with the logging output? It should say
what the value of matchPath is. This would be a debug-level logging
statment indicated by a line stating:
Selecting module for path matchPath
After getting the logging opened up, my results are matchPath
11 matches
Mail list logo