Mike: We were getting the org.apache.acess.client... I'll check with my server admin to make sure PARENT_LAST is set on the war file also. I would greatly appreciate if you can share/find out what's done to get axis working in WPS5. The IBM tech support wasn't much helpful, all they suggested was that I need to create the properties files for the commons-logging.
Thanks. - Yaxiong -----Original Message----- From: Mike Burati [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 12, 2004 9:48 AM To: '[EMAIL PROTECTED]' Cc: Graeme Riddell Subject: RE: Axis and WebSphere Portal server? I believe we have used AXIS from within WPS5 here, I can check with the person(s) involved. Which classes are not found when you run your app on WPS? Also, you can set PARENT_LAST on either or both of the EAR and the WAR in the WAS5 administration tool. Make sure it's set on the WAR (web application/module), and not just on the EAR (enterprise app). -----Original Message----- From: Lin, Yaxiong [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 12, 2004 10:41 AM To: '[EMAIL PROTECTED]' Subject: Axis and WebSphere Portal server? My portal app runs fine on my WSAD 5.1 with WebSphere portal tool kit 5.0 (test portal server) running on XP, but when it's deployed on WebSphere portal server 5 on Win2000 server, it caused class not found exception on classes appear to be used by axis. The app uses soap package Axis 1.1 from Apache. All packages required by axis including axis.jar, common logging, etc. are all in WEB-INF/lib. So, we moved axis.jar, etc. to the server path, but still getting class not found exception on other classes. Also we have created the common logging properties files, and make sure class loader mode is set to PARENT_LAST. We were wondering if anyone has successfully deploy the portal app with Axis packages? Thanks. - Yaxiong Lin Mayo Clinic Rochester, MN 55905
