Ive got commons-logging in there. But dont think its setup properly though ill go take another look. That stacktrace comes from websphere, but there doesnt seem to be any other info about the error logged anywhere. Ill check my logging properties again in the morning and see if I can get it to give me some more .
-----Original Message----- From: Dirk Markert [mailto:[EMAIL PROTECTED] Sent: Wednesday, 11 June 2003 19:49 To: Struts Users Mailing List; [EMAIL PROTECTED] Subject: Re: Is it possible to use struts 1.1 with WebSphere 4? Do you have logging enabled? From looking at the struts source, I would guess you will get more detailed information regarding the exception. Currently it is not clear where exactly the exception happens. Knowing the exact line we can perhaps locate the error. *************************************************************** AH> We need to see if its possible to make our big complex application work on AH> WebSphere 4. We had it working on 5. AH> The ui is done in struts and it was suggested that struts1.1 couldnt be used AH> with WepSphere 4 as WS4 uses the 2.2 servlet API. I figured this shouldnt be AH> a problem as struts supports 2.2 and doesnt need 2.3 AH> Nevertheless I havent even been able to get a simple test application to run AH> on WAS4. (Something of a struts equivalent to hello world". - One action AH> that does a println to the response to prove you reached it) AH> This test app deploys and runs just fine in tomcat 3.3.1a (a servlet api 2.2 AH> container) and of course in 4.0.6, but on websphere the ActionServlet dies AH> in the init method with: AH> SRVE0100E: Did not realize init() exception thrown by servlet action: AH> javax.servlet.UnavailableException: Parsing error processing resource path AH> at AH> org.apache.struts.action.ActionServlet.initModuleConfig(ActionServlet.java:9 AH> 52) AH> at org.apache.struts.action.ActionServlet.init(ActionServlet.java:468) AH> at javax.servlet.GenericServlet.init(GenericServlet.java:258) AH> at AH> com.ibm.servlet.engine.webapp.StrictServletInstance.doInit(ServletManager.ja AH> va:802) AH> at AH> com.ibm.servlet.engine.webapp.StrictLifecycleServlet._init(StrictLifecycleSe AH> rvlet.java:137) AH> at AH> com.ibm.servlet.engine.webapp.PreInitializedServletState.init(StrictLifecycl AH> eServlet.java:243) AH> at AH> com.ibm.servlet.engine.webapp.StrictLifecycleServlet.init(StrictLifecycleSer AH> vlet.java:103) AH> at AH> com.ibm.servlet.engine.webapp.ServletInstance.init(ServletManager.java:388) AH> at javax.servlet.GenericServlet.init(GenericServlet.java:258) AH> at AH> com.ibm.servlet.engine.webapp.ServletManager.addServlet(ServletManager.java: AH> 84) AH> at AH> com.ibm.servlet.engine.webapp.WebAppServletManager.loadServlet(WebAppServlet AH> Manager.java:226) AH> at AH> com.ibm.servlet.engine.webapp.WebAppServletManager.loadAutoLoadServlets(WebA AH> ppServletManager.java:357) AH> at AH> com.ibm.servlet.engine.webapp.WebApp.loadServletManager(WebApp.java:1001) AH> at com.ibm.servlet.engine.webapp.WebApp.init(WebApp.java:133) AH> at com.ibm.servlet.engine.srt.WebGroup.loadWebApp(WebGroup.java:234) AH> at com.ibm.servlet.engine.srt.WebGroup.init(WebGroup.java:139) AH> at AH> com.ibm.servlet.engine.ServletEngine.addWebApplication(ServletEngine.java:63 AH> 3) AH> at com.ibm.ws.runtime.WebContainer.install(WebContainer.java:36) AH> at com.ibm.ws.runtime.Server.startModule(Server.java:615) AH> at com.ibm.ejs.sm.active.ActiveModule.startModule(ActiveModule.java:509) AH> at com.ibm.ejs.sm.active.ActiveModule.startAction(ActiveModule.java:355) AH> at com.ibm.ejs.sm.active.ActiveObject.startObject(ActiveObject.java:709) AH> at com.ibm.ejs.sm.active.ActiveObject.start(ActiveObject.java:131) AH> at java.lang.reflect.Method.invoke(Native Method) AH> at AH> com.ibm.ejs.sm.agent.AdminAgentImpl.activeObjectInvocation(AdminAgentImpl.ja AH> va:93) AH> at AH> com.ibm.ejs.sm.active.ActiveObject.invokeContainedObject(ActiveObject.java:5 AH> 12) AH> at AH> com.ibm.ejs.sm.agent.AdminAgentImpl.activeObjectInvocation(AdminAgentImpl.ja AH> va:110) AH> at AH> com.ibm.ejs.sm.agent.AdminAgentImpl.invokeActiveObject(AdminAgentImpl.java:6 AH> 2) AH> at AH> com.ibm.ejs.sm.agent._AdminAgentImpl_Tie._invoke(_AdminAgentImpl_Tie.java:80 AH> ) AH> at AH> com.ibm.CORBA.iiop.ExtendedServerDelegate.dispatch(ExtendedServerDelegate.ja AH> va:506) AH> at com.ibm.CORBA.iiop.ORB.process(ORB.java:2294) AH> at com.ibm.CORBA.iiop.OrbWorker.run(OrbWorker.java:185) AH> at com.ibm.ejs.oa.pool.ThreadPool$PooledWorker.run(ThreadPool.java:95) AH> at com.ibm.ws.util.CachedThread.run(ThreadPool.java:122) AH> Is this just something Im doing wrong (ideas on what would be appreciated!), AH> or is it really true that you cant use struts 1.1 with websphere 4? AH> <useless-information> AH> Its a simple app I banged together with one action that writes a string AH> directly to the response. AH> Its got a whole bunch of libs in WEB-INF/lib as Im not sure what struts AH> needs and doesnt: AH> ie: AH> commons-beanutils.jar AH> commons-collections.jar AH> commons-dbcp.jar AH> commons-digester.jar AH> commons-fileuplaod.jar AH> commons-lang.jar AH> commons-logging.jar AH> commons-pool.jar AH> commons-resources.jar AH> commons-validator.jar AH> jakarta-oro.jar AH> jdbc2_0-stdext.jar AH> log4j-1.2.7.jar AH> struts.jar AH> My logging properties are set up to use log4j, though Im not calling the log AH> in my action. AH> Various config files are in my WEB-INF AH> struts-config.xml AH> tiles-def.xml AH> validation.xml AH> web.xml AH> struts-config has been set up as simple as possible - just maps one path to AH> one action. The other files are untouched and would be same as whats in the AH> struts blank war. AH> </useless-information> AH> --------------------------------------------------------------------- AH> To unsubscribe, e-mail: [EMAIL PROTECTED] AH> For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- 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]
