RE: WebSphere 5.1 does not run Web Applications running Axis SOAP Engine

[ae...@rbc.com]

I am successfully running a web application on WAS 5.1 using Axis 1.1.  I have had some problems with Axis1.2RC3 and WAS 5.1 but I got over those by using Shared libraries to contain all the Axis jars and PARENT_LAST as the classloader policy.

I also had to specify a name-value pair assigning the  fully-qualified class name of the LogFactory implementation to property  org.apache.commons.logging.LogFactory in file commons-logging.properties, and  place this file in the classpath to force WAS to use the Apache implementation of LogFactory instead of the IBM one - see http://www-1.ibm.com/support/docview.wss?uid=swg27004610 (but this could be just for WAS on the iSeries).
  
I  added the commons-logging.properties file to a config directory which was in a shared library associated with the application and Axis was happy and the web service worked. 

I also called IBM support for help but in the end I ended up finding the solution through google.



-----Original Message-----
From: Tysnes Are Thobias [mailto:are.tysnes@edb.com]
Sent: 04 May 2005 8:54 
To: axis-user@ws.apache.org
Cc: axis-dev@ws.apache.org
Subject: WebSphere 5.1 does not run Web Applications running Axis SOAP
Engine



Hello!

We are running WebSphere Application Servers in production and are
planing
on deploying a Web Application (Web Services, Axis 1.2 and Castor).

There are some issues deploying Web Applications containing Axis in
WebSphere
because IBM is using a "home-made" version of Axis inside WebSphere.
I did contact IBM support and they can tell me that it is not possible
to
run Web Applications containg Axis on WebSphere 5.1.

Can anyone confirm this !? Do we realy have to change our Application
Server
because we decided to use Axis as SOAP Engine !?

Cheers,
Are T. Tysnes
__________________________________________________________________________________________________________________________________

This e-mail may be privileged and/or confidential, and the sender does not waive any related rights and obligations.
Any distribution, use or copying of this e-mail or the information it contains by other than an intended recipient is unauthorized.
If you received this e-mail in error, please advise me (by return e-mail or otherwise) immediately.  

Ce courrier électronique est confidentiel et protégé. L'expéditeur ne renonce pas aux droits et obligations qui s'y rapportent.
Toute diffusion, utilisation ou copie de ce message ou des renseignements qu'il contient par une personne autre que le (les) destinataire(s) désigné(s) est interdite.
Si vous recevez ce courrier électronique par erreur, veuillez m'en aviser immédiatement, par retour de courrier électronique ou par un autre moyen.

Re: WebSphere 5.1 does not run Web Applications running Axis SOAP Engine

[Catalin Grigoroscuta <c....@moodmedia.ro>]

Hi,

I know this is off topic, but I think it may help you.
There is a much cleaner way to setup LogFactory on Websphere, without 
doing the PARENT-LAST trick. See 
http://www-1.ibm.com/support/docview.wss?uid=swg27004610 for details

aedemar.cooke@rbc.com wrote:

>I also had to specify a name-value pair assigning the  fully-qualified class name of the LogFactory implementation to property  org.apache.commons.logging.LogFactory in file commons-logging.properties, and  place this file in the classpath to force WAS to use the Apache implementation of LogFactory instead of the IBM one - see http://www-1.ibm.com/support/docview.wss?uid=swg27004610 (but this could be just for WAS on the iSeries).
>  
>I  added the commons-logging.properties file to a config directory which was in a shared library associated with the application and Axis was happy and the web service worked. 
>
>  
>