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:After getting the logging opened up, my results are <matchPath> is "" (blank, not null) when running through Cactus/StrutsTestCase, but not when running through a browser. Odd. I guess this is not a Struts issue per se. I'll take this up on the Cactus list when I get a chance.
Selecting module for path <matchPath>
Erik
--
To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org>