Win a copy of The Java Performance Companion this week in the Performance forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Axis2 vs. Axis1

 
Ricky Murphy
Ranch Hand
Posts: 31
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,

have been working with Axis-1 and trying to learn Axis-2. I am reading the Axis2 doc, etc. It looks like that I need to (at least it is advocated) deploy axis2.war into Tomcat first and all my future services will be deployed into axis2. That means axis2 app itself serves as an entry point for all services. However, in Axis-1, even this approach is valid, I may also develop my service app with axis.jar included as a ref library. I could then deploy myApp.war under Tomcat. is this kind of development/deployment approach still OK with Axis-2, any examples, especially work with Spring framework will be much helpful. Anyone please shed some light.

Thank you so much!!!

Rick
 
Balaji Loganathan
author and deputy
Bartender
Posts: 3150
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Ricky,
I am not getting whats your first question is about ?

Regarding Axis2-Spring
You can good info at http://ws.apache.org/axis2/1_1/spring.html

Sample code is also available at http://svn.apache.org/viewvc/webservices/axis2/trunk/java/modules/samples/pojoguidespring/

Regards
Balaji
 
Ulf Dittmer
Rancher
Posts: 42968
73
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Both Axis 1 and Axis 2 are ordinary Java web apps. They can be used standalone as they are, or they can be incorporated into other web apps, and you can develop and deploy them any way you wish (war file or directory hierarchy). Does this answer your question?
 
Ricky Murphy
Ranch Hand
Posts: 31
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thank you Balaji and Ulf.

I think that you kind of answered my question. let me rephrase it.

in Axis-1, there are basically two options to deploy a web service:
1. deploy axis.war into /webapps, so that axis is a regular web application. After I develop my own web service app, I can then loaded inside the "axis" app. that I just deployed. This way, I let "axis" app to manage my service. if I develop more services, I install them the same way into existing "axis" application. As you can see, "axis" application becomes an entry point to all my services.

This method is explained everywhere in Axis-2 service development and deployment.

2. The other way in Axis-1 is that I development my service app, say myApp, in myApp's lib directory, I put an axis.jar and other jars that axis-1 needs. After all the development is done, I deploy this myApp.war under /webapps, so Tomcat in this case will manage this myApp (i.e. my service app). If i need to develop more services then I do the same. therefore, under /webapps I may end up with many axis services, each one is a separate application managed by Tomcat, and inside each app's lib, you will find axis.jar and other axis needed jar file.

This method, in Axis-2, is not explained anywhere, at least I didn't see it, that was the reason I asked if I can do it this way, any document or examples that I can find out. The jar files in axis-2 seems to be a lot.

Yes, I have looked at the doc to integrate Spring with Axis-2 mentioned at the Axis web site. and that is also related to the method 1 above.

Thank you all and I hope this makes it more clearer.

Rick
 
Ulf Dittmer
Rancher
Posts: 42968
73
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The second method works with Axis2 as well. Yes, it's a lot of jar files (even more if you add WS-Security), but that isn't really a problem.

The only thing to watch out for is that the URL that is configured for the Axis servlet doesn't overlap with any URL used by the rest of the web app.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic