Another weird thing that may be connected to the issue is the following. When I start the administration console of WLS9.2 (which is built using struts 1.2.7 as well) I get the following warning in the log file:
<Info> <Console> <BEA-240002> <Struts module is configured to use com.bea.console.internal.ConsolePageFlowRequestProcessor as the request processor, but the ><controller> element does not contain a <set-property> for "controllerClass". Page Flow actions in this module may not be handled correctly.> Nevertheless the administration console works fine. Could there be a possible conflict between the built-in administration console and my deployed application, as they both use struts 1.2.7? -----Ursprüngliche Nachricht----- Von: Martin Burkhart [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 22. September 2006 15:40 An: user@struts.apache.org Betreff: Migrating Struts application from weblogic 8.1 to 9.2 Hi Im trying to get my struts 1.2.7 application running properly on weblogic 9.2. It is working fine on weblogic 8.1 but page forwarding doesn't seem to work on 9.2. Here is what I did to the application in order to being able to compile it with the weblogic application compiler: - Made web.xml compliant with Servlet 2.4/JSP2.0: <web-app version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> - Upgraded from JSTL 1.0 to JSTL 1.1 The application compiles fine and the login page appears. But when the users logs in correctly, a mapping.findForward("/success"); command leads to a "404 not found" error. The struts 1.2.7 demo applications are running nicely, though. Did anybody succeed in doing a similar thing or experience similar errors? Any help is appreciated. --Martin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
