This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
No it's not possible. There are two reasons; one, WebSphere (not WSAD -- WebSphere the application server -- we need to be clear here) does not use Axis, as it uses its own internal web services engine. So if you're generating to WebSphere, you're not using Axis anyway.
If you are generating your code directly to Axis (which some later versions of WSAD and certainly RAD allow) then it's also impossible to change the version, but that's because the code-generation logic cannot be changed. To get to the newest version of axis, you have to upgrade to the newest version of your development environment.
I should have been more clear on my initial post (sorry for the lack of details).
I am using WSAD 5.1.2 and I am using the wizard to create a Web service Client to consume an external web service. When this is done, it drops axis.jar (version 1.0) in the project along with log4j-2.1.6.jar.
I would like to have it use the axis 1.1 jar to create the client stubs and, if possible, the log4j-2.1.8.jar at a minimuim.
So I think the reply to my initial message describes the web service deployment side ... and it still may not be possible to change how the client stubs are generated ... but I wanted to double check.
Joined: Aug 10, 2001
You could write an Ant Script (perhaps) to change out the Axis JAR file, but there's no guarantee that the generated stubs would work with the new JAR file -- it should but that's not a guarantee.