Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Cloud/Virtualization forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

is it possible for Axis2 and Axis1 co-exist in client application?

 
wenqi wang
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am currently responsible for designing new web service components,
that need to integrate web service client in the old system that use
Axis1. This client component is required to retrieve binary data
(attachement) from new web service server. I am trying to use Axis2
implementing new server . However I concerned about the conflict
between Axis1 jar and Axis2 jar files in client component, because we
cannot get rid of Axis1.

would you please give me some advise?
 
Ulf Dittmer
Rancher
Pie
Posts: 42967
73
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Welcome to JavaRanch.

Axis 1 uses the "org.apache.axis" package, while Axis 2 uses "org.apache.axis2", so the core classes shouldn't conflict with each other. But the versions come with some auxiliary libraries that use differing versions in Axis 1 and 2, like JAX-RPC, SAAJ, WSDL and Commons Logging. Some of those (like Logging) present not problem, while others (like WSDL) may or may not.

I'd guess that you have a fair shot at making this work.
 
wenqi wang
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Ulf,

Thank you very much for the response. I will try.

If I have another instance deployed for my application that located with the same server as old one that used axis 1, I think it won't have any problem of conflict between axis1 and axis2 jar file as well as auxiliary files. what do you think? Many thanks

regards, hongwei
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic