I have converted a simple 'hello world' java bean into a web service using WSAD 5.1.2. It has created a seperate ear-war projects for both server and client and I am able to access the web service from the sample web client generated by WSAD 5.1.2.
Now, before deploying this ear files in WAS 5.0 I want to make use of Apache AXIS jar files so that at the end I can deploy these ear web services successfully on both WAS 4.0 and WAS 5.0 and I dont want to rely on the soap implementations provided by each of these server versions as they can be different. So I have manually placed all the axis(axis-1_2RC1) jar files in each(client and server web applications) of web applications lib directory and exported them as ear files using WSAD and deployed these two ear files in WAS 5.0.
It was my understanding that in order to deploy a web service using axis, you needed to install it. This goes a bit beyond putting it's jar files in the lib directory of the applications. Speaking from a tomcat perspective, axis deploys as a separate WAR file. Then in order to publish a web service using axis, you need to make your classes and jars available to the axis application and modify some configs (there's more than one way to do this).
My suggestion (and it may be a bad one) is to create a .war file called axis and import the axis stuff into it. Deploy the .war file using the admin console for WebSphere. Then push you web services to the axis app.
Go here for installation instructions. Of course, this is for tomcat but you'll have to be intuitive to figure out what to do as far a WAS is concerned.
No more rhymes! I mean it!<br /> <br />Does anybody want a peanut?
I got an fix to my problem. Instead of relying on WSAD's WebSphere 5.0 runtime environment for developing web services I used WSAD's AXIS runtime environment and without any changes I am able to deploy in standalone WAS 5.0
Thank you all anyway, Kumar.
Always! Wait. Never. Shut up. Look at this tiny ad.