Using WAS 6.1 client with Tomcat 6.0
Hello, Web application that I'm developing needs to access EJBs deployed within WebSphere Application Server 6.1. The way to communicate with WAS described in documentation is to use WAS client, namely com.ibm.ws.admin.client_6.1.0.jar. The problem with this jar is that it contains javax.servlet.http.HttpServlet class and others, so it won't load from application's WEB-INF/lib as offending. Thus I have to place it into lib/ext directory in JRE. This works until the compilation of JSP is required - then Jasper fails since it uses classes loaded previously from com.ibm.ws.admin.client_6.1.0.jar instead of those from jsp-api.jar and servlet-api.jar. JSP-related classes in com.ibm.ws.admin.client_6.1.0.jar implement Servlet 2.4/JSP 2.0 while Jasper in Tomcat 6.0 requires 2.5/2.1. Is there any smart way to get this working, I mean using JSPs along with WAS 6.1 client? -- View this message in context: http://www.nabble.com/Using-WAS-6.1-client-with-Tomcat-6.0-tp23719994p23719994.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Using WAS 6.1 client with Tomcat 6.0
From: zeiss [mailto:ze...@tut.by] Subject: Using WAS 6.1 client with Tomcat 6.0 The problem with this jar is that it contains javax.servlet.http.HttpServlet class and others, so it won't load from application's WEB-INF/lib It may appear to work if you put it in the JRE's ext directory, but that only masks the classloading mess that's created. You need to take the WebSphere jar apart, remove the conflicting classes (anything starting with java or javax), put it back together, and then place it in WEB-INF/lib (and nowhere else). Ugly, but necessary. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org