• Post Reply Bookmark Topic Watch Topic
  • New Topic

Migration from Axis 1.2 to Axis2  RSS feed

 
Nagarjun Bollam
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All,

I have an existing application which currently runs on Axis 1.2 (on Jboss server)
I am willing to write a new application that would run Axis 2 (since it supports REST as well).

I have two choices:

1. Migrate my existing application to Axis 2 and deploy both existing and new applications on Axis 2 only.
2. Keep my existing application untouched and run both Axis 1.2 and Axis 2 engines for existing and new applications respectively.
3. Generate and compile my existing application in Axis 1.2, but deploy it on Axis 2 run time. (Is this possible at all?)

Which of the choices above would you suggest?

I have also used Handlers in my existing application (from my understanding on Axis migration, I am required to re factor such classes). How much effort would migration take?

Is there a possibility to implement option 2? I believe there will be a performance hit when I deploy both axis engines, correct me if I am wrong (I am OK with this if option 1 takes huge effort).
If option 2 can be implemented, where exactly can I change the port number for Axis 1.2 and Axis 2 versions in order to run both the engines in parallel.

If option 3 is possible, some one please shed some light on the procedure.

Thanks in advance.
 
William Brogden
Author and all-around good cowpoke
Rancher
Posts: 13078
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
As I understand it, there are major differences between Axis 1.2 and Axis2 = the 1.2 was considered too damaged to fix so Axis2 is a complete rewrite. Axis 1.2 is not maintained and the last release was in 2006.

For more, see this artice on migrating from 1.2 to 2

As I recall, the supposed support for RESTful architecture in Axis 2 is a real kludge. You would be much better off starting from scratch and redesigning for a RESTful service, assuming you don't need features only SOAP can provide.

Bill
 
Nagarjun Bollam
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
William Brogden wrote:As I understand it, there are major differences between Axis 1.2 and Axis2 = the 1.2 was considered too damaged to fix so Axis2 is a complete rewrite. Axis 1.2 is not maintained and the last release was in 2006.

For more, see this artice on migrating from 1.2 to 2

As I recall, the supposed support for RESTful architecture in Axis 2 is a real kludge. You would be much better off starting from scratch and redesigning for a RESTful service, assuming you don't need features only SOAP can provide.

Bill


Thanks for the reply sir.

As I recall, the supposed support for RESTful architecture in Axis 2 is a real kludge
I didn't understand this statement exactly. Can you please elaborate. Also, as long as it is possible, I want to maintain my existing application in SOAP only (be it Axis 1.2 or Axis 2). My New application would be in REST. In other words, I want to re-use the already generated SOAP requests (via Axis 1.1 and 1.2) on my existing application. I assume, SOAP support is the only option for me. Please correct me if I am wrong.

Also, some of my above questions are still unanswered. Can you please let me know if it is possibility and feasibility to implement option 2 and option 3?
 
William Brogden
Author and all-around good cowpoke
Rancher
Posts: 13078
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
If you have to keep the SOAP services going, then AXIS 2 is the obvious choice since it is the only one actively supported by Apache. It is also supposed to be considerably more efficient in terms of memory and CPU use. AXIS 2 is a completely different code base with no commonality so your 3 is right out.

In my last encounter with AXIS 2, years ago, it appeared they were supporting REST by turning a REST request into a SOAP request, submitting to the SOAP engine then reconverting back to a RESTful style response. Thats a kludge in my book. It may actually work better than it sounds - if you go this route, please get back to the Ranch with your results, this question comes up from time to time so it would be a help to hear from somebody who has done it.

Bill
 
Ulf Dittmer
Rancher
Posts: 42972
73
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I agree with William that you should not use whatever REST support there is in Axis - use a proper REST tool for that. You should be able to run Axis and (say) Jersey within the same web app w/o problem.
 
Nagarjun Bollam
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks for the help folks.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!