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.
I'm planning to put together a small presentation to my team about the migration of web services from Websphere 5.0 to websphere 5.1. I was wondering if anyone could give me some pointers on the migration issues when deploying a web services on V5.0 which was created using the Websphere studio 5.1.
My little experiment: I've developed a sample application and provided webservices capability using Websphere studio 5.0 and generated web services for the same sample application using web sphere studio 5.1
Here is what I observed during the transition from websphere 5.0 to websphere 5.1
1.) In V5.0, when we use the wizard to create a web service, it generated 4 wsdl files and a proxy along with dds.xml and soap.xml and testingjsp. 2.) I pacakage everything into an ear and imported the same ear on to my V5.1 websphere studio. 3.) when I deployed this ear on my websphere 5.1 server, everything worked smoothly without any problems.
So I believe upward comaptibility of web services in websphere is possible.
Now I created webservices for the same sample application, this time using V5.1 and exported the ear.
Now When I import the ear onto my v5.0 studio developer. It gives me some compile time errors.
I beleive there are some jars missing ad can be found at IBM web services developer pack.
Web services in websphere is not backward comapatible I guess.
Can anyone please describe the migration issues, when migrating a web services application from V5.1 to V5.0
Thanks very much kiran
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com