WEB-INF/classes contents be JAR?

[sphereproj]

Hi All,
Can the contents of the WAR file WEB-INF/classes directory contain jars? It seems that if I try to override a class in the lib folder by placing a jar in this this folder it does not quite work.
In 4.0.3 ibm added a new version of ActionServlet in the WEB-INF/classes folder however they did not modify the manifest file in WEB-INF/lib/seadmin_code.jar to include this new path. I jarred the files ibm overrides in the classes folder and added the name of this jar to the manifest.mf classpath section of seadmin_code.jar. However, now I am getting VerifyError problems when I try to start the admin (even if these are just classes, it still does not work):

X Servlet Error: (class: com/ibm/ejs/sm/web/common/CommandManagerImpl, method: <init> signature: (Lorg/apache/struts/action/ActionServletV) Incompatible object argument for method call: java.lang.VerifyError: (class: com/ibm/ejs/sm/web/common/CommandManagerImpl, method: <init> signature: (Lorg/apache/struts/action/ActionServletV) Incompatible object argument for method call
at com.ibm.ejs.sm.web.common.LogonAction.perform(LogonAction.java:242)
at org.apache.struts.action.ActionServlet.processActionInstance(ActionServlet.java:960)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:869)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:343)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager.java:827)
at com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycleServlet.java:167)
at com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServlet.java:297)
at com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycleServlet.java:110)
at com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java:472)
at com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletManager.java:1012)
at com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManager.java:913)
at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:665)
at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:331)
at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:117)
at com.ibm.servlet.engine.srt.WebAppInvoker.doForward(WebAppInvoker.java:124)
at com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:218)
at com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:67)
at com.ibm.servlet.engine.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java:106)
at com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:125)
at com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener.java:315)
at com.ibm.servlet.engine.http11.HttpConnection.handleRequest(HttpConnection.java:60)
at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:323)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:252)
at com.ibm.ws.util.CachedThread.run(ThreadPool.java:137)

 

[Guest_imported]

I found out the problem regarding verify problems to be due to the fact that websphere uses a different later release of the xerces.jar jar. So make sure that your code is compiled with this samme jar.