I have deployed an application I had working with JRun 4.1 on iPlanet 6.5.
Once I initialized log4j using the initialization servlet and added
xercesImpl.jar to the application the dispatcher loaded fine. The logging
demonstrates that the Loader also read my maverick.xml a-okay.

When I try to run a command (https://myhost/NASApp/MASTER/securityTest.m);
however,  I get the following:

15:52:47,941 DEBUG [Dispatcher] Command servlet path is:  /securityTest.m 
15:52:47,941 DEBUG [Dispatcher] Command context path is:  /NASApp/MASTER
15:52:47,942 INFO  [Dispatcher] Servicing command:  securityTest 
15:52:47,950 INFO  [CommandBase] Switching to view:  loginRequired 
15:52:47,951 DEBUG [DispatchedViewFactory] Setting 1 params 
15:52:47,951 DEBUG [MaverickContext] Creating transform step 0 
15:52:47,951 DEBUG [MaverickContext] ...which is the LastStep 
15:52:47,952 DEBUG [DispatchedViewFactory] Forwarding to
mav/loginRequired.jsp 
15:52:47,952 DEBUG [LastStep] Getting real response

and an HTTP 404 error. 

The JSP is indeed in the /mav directory and I can bring it up fine via the
URL https://myhost/NASApp/MASTER/mav/loginRequired.jsp.


I see a slightly different behaviour with a command that uses the default
(null?) controller:

    <command name="helloWorld">
      <!-- helloWorld views -->
      <view name="success" path="mav/helloWorld.html"/>
    </command>

15:03:10,557 DEBUG [Dispatcher] Command servlet path is:  /helloWorld.m 
15:03:10,557 DEBUG [Dispatcher] Command context path is:  /NASApp/MASTER 
15:03:10,558 INFO  [Dispatcher] Servicing command:  helloWorld 
15:03:10,558 INFO  [CommandBase] Switching to view:  NO CONTROLLER DEFINED 
15:03:10,558 DEBUG [MaverickContext] Creating transform step 0 
15:03:10,558 DEBUG [MaverickContext] ...which is the LastStep 
15:03:10,559 DEBUG [DispatchedViewFactory] Forwarding to mav/helloWorld.html

15:03:10,559 DEBUG [LastStep] Getting real response

Instead of the regular 404 I get a page that says: Error: 404 SC_NOT_FOUND.
No detailed message. I speculate that this is the error being thrown
explicitly by Dispatcher.service(169).

I don't find any stack traces anywhere and I'd expect an exception to pop up
somewhere if it was a Servlet 2.2 vs. 2.3 problem. Where should I begin
looking?


John-Mason Shackelford

Software Developer
NCS Pearson - Measurement Services
2510 North Dodge St.
Iowa City, IA 52245
319-354-9200x6214
[EMAIL PROTECTED]

**************************************************************************** 
This email may contain confidential material. 
If you were not an intended recipient, 
Please notify the sender and delete all copies. 
We may monitor email to and from our network. 
****************************************************************************


-------------------------------------------------------
This SF.NET email is sponsored by: Take your first step towards giving 
your online business a competitive advantage. Test-drive a Thawte SSL 
certificate - our easy online guide will show you how. Click here to get 
started: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0027en
[INVALID FOOTER]

Reply via email to