MyEclipse :: View topic - XFire Vs Axis

MyEclipse

Web Services - XFire Vs Axis

wilson_2 - Jul 27, 2006 - 10:32 PM
Post subject: XFire Vs Axis

I know that MyEclipse has given its backing to Xfire. But I want to know if Xfire is really the best option to develop web services. I know Axis. What are the advantages from Xfire over Axis?

support-rkalla - Jul 27, 2006 - 11:11 PM
Post subject:

wilson,
I know that the team that decided on XFire took the evaluation seriously and looked at everything from bug reports to outstanding issues to community activity and support levels. I will ask them to weigh in with their decision if/when they get a chance. We are in the midst of QA right now and everyone is swamped so replies might not come immediately.

taylodge - Dec 07, 2006 - 01:57 PM
Post subject:

I am very interested in the answer to this question!!!!!!

Anything further to add?

support-rkalla - Dec 07, 2006 - 03:05 PM
Post subject:

Sorry guys, the WS team is very busy right now and haven't had a chance to weigh in on this thread. I'll pester them when things calm down.

daorriss - Dec 21, 2006 - 07:20 PM
Post subject:

I'll add my two cents if I may.

First Axis is INCREDIBLY fussy when it comes to interfacing with .NET-based web services. I had a VERY hard time making code that would cleanly and consistenly call a web service that was written in C#. By the same token, the WebService consumers (that are based on Axis) in WebLogic 8.1 worked very well doing the same thing and were *much* easier to use. So it would appear that WebLogic makes substantial changes to the Axis code base to give it the increased ease of use for developers.

This said XFire has more library bloat compared to Axis and that *does* drive me a bit nuts. But XFire has also (in my initial tests) shown itself to be more robust in the same situations where Axis simply wouldn't do the job (without modifying generated code).

So there you have my thoughts on the subject... Hope you find them helpful.

support-rkalla - Dec 21, 2006 - 08:18 PM
Post subject:

Anybody have any idea what Glassfish/Sun App Server is using to implement the new JEE 5 web services that Sun pushed really hard as having fantastic MS-integration?

daorriss - Feb 21, 2007 - 08:49 PM
Post subject:

FYI: here's a stack comparison courtesy of the writers of XFire.. http://xfire.codehaus.org/Stack+Comparison

alukic - Apr 16, 2007 - 07:07 PM
Post subject: XFire 2 migration

It seems that XFire is merging with Celtix and then becoming the part of Apache foundation. Maybe it is not the best thing for MyEclipse to be working on a tool that will become useless in about year or so. Read this post for more details: http://swik.net/Axis-vs-XFire

support-rkalla - Apr 16, 2007 - 07:21 PM
Post subject:

alukic,
I don't follow the "useless" assertion... we have very strong ties to the XFire team, where ever the project is going with it's stack we will likely tread as well.

alukic - Apr 16, 2007 - 08:00 PM
Post subject:

Alright, fair enough. I have been MyEclipse user for a while now, and it is my preferred platform. For that reason I would hate it to go down some path that may not be useful for majority of dev community. When I said useless, I meant that they will be changing their complete codebase, and it may take them a while to get the XFire stable enough for people to use it. Axis has already done this huge step so it is fairly stable. Hence, developing tools for XFire may become a challenging task. I appreciate the fact that you guys are working tightly together with XFire team, but when you say "likely" does that mean "definitely", "possibly" or "some unknown degree of certainty"?
Don't get me wrong, I am a big fan of MyEclipse and relly enjoy working with it. That is why I am bit concerned, that's all. Best of luck.

support-rkalla - Apr 16, 2007 - 08:12 PM
Post subject:

We certainly understand and will continue to deliver the best user-experience we can with the technology stacks we choose to build on. We won't ship anything shoddy.

tomeksz - Apr 17, 2007 - 08:07 PM
Post subject: Re: XFire 2 migration

alukic wrote:

First of all XFire won't become useless so easy :) XFire will be developed as long as needed ( as long users have some issue or improvement request ).
Yes, XFire is merging with Celtix, but you can think of it as of XFire 2.0, so any migration from XFire 1.x to XFire 2.x will be as easy as possible, so you can move to XFire 2.0 without any (or minimal ) modification to your code.

gcruscoe - Apr 19, 2007 - 02:29 PM
Post subject:

I'm confused why everyone hasn't embraced the JAX-WS for their web services. It is part of the Java EE 5 spec and therefore will be supported on every Java EE 5 Application Server. This seems like the starting place for web services. Adding other toolkits would be a bonus, but not a starting point. I have used the JAX-WS and it is extremely easy to use, well documented, and performed very well.

I'm sorry about the ties to the XFire codebase and team (I really liked that product before I started using the Java EE 5 Web Services), but those ties are leading you in the wrong direction. I love Eclipse and MyEclipse, and have converted over almost every company I've been at to use them. However, I currently cannot recommend them over Netbeans if the shop is working on Java EE 5 application servers.

I know the Eclipse WTP is looking at Axis2 and you guys are talking about XFire, and to me none of this makes sense. I am simply beside myself waiting for MyEclipse to catch up to netbeans when it comes to Java EE 5. Some one needs to become an expert at it to understand all of the benefits it provides so that they can be ported to Eclipse. I love Eclipse and MyEclipse, but Java EE 5 is the most important technology right now. BTW, I have just downloaded the 5.5M2 for 3.2.2 so I will be checking out the Java EE 5 support of MyEclipse today. I really hope it is better than what I've seen in the WTP, because even though it is claimed to be Java EE 5, it doesn't even come close.

I would love to sell more MyEclipse licenses for you, and I look forward to working with your Java EE 5 updates!

Cheers,
Geoff

tomeksz - Apr 19, 2007 - 04:37 PM
Post subject:

You forgot about one small,tiny problem, lot of ppl still use java 1.4 ( e.g because of commercial servers installed on production env ) and can't move to java 5 so JAX-WS is useless for them ( e.g. for me ).

support-rkalla - Apr 19, 2007 - 04:46 PM
Post subject:

Geoff,
We aren't going to be dropping any ball on technology that makes developers lives easier. I believe researching JAX-WS is on our 6.0 TODO list right now.

gcruscoe - Apr 19, 2007 - 04:48 PM
Post subject:

I'm so sorry to hear it. Keep fighting the good fight; eventually everyone will be up to Java 5!

The development productivity I've seen with Java 5 and Java EE 5 has been astronomical. Its the best of everything. Although I have to admit that until MyEclipse catches up with netbeans they are losing customers everyday to Netbeans 5.5 and beyond, because of the ease of development. I'm rooting for 'em though.

tomeksz - Apr 20, 2007 - 07:39 PM
Post subject:

btw, XFire supports JAX-WS, so you can use it right now, without warring about server support for it:)

gcruscoe - Apr 25, 2007 - 09:59 PM
Post subject:

That is really good news. So I can use a newer version of XFire say on Tomcat and use the JAX-WS annotations to put everything together?

That would be very cool.

tomeksz - Apr 25, 2007 - 10:14 PM
Post subject:

Yep, you can use JAX-WS on any webserver and then remove xfire libs and put your classes on JEE5 webserver and everything should still work ;) Pure XFire magics ;)

DavidVTHokie - Apr 26, 2007 - 05:42 PM
Post subject:

Riyad - Glad to hear you folks have JAX-WS on your radar. I can't wait until you guys tie it in.

arungupta - Jul 03, 2007 - 05:34 PM
Post subject:

support-rkalla wrote:

Anybody have any idea what Glassfish/Sun App Server is using to implement the new JEE 5 web services that Sun pushed really hard as having fantastic MS-integration?

GlassFish (http://glassfish.java.net) has Metro (http://metro.dev.java.net) - the complete Web services stack. Metro consists of highly-performant JAX-WS (http://jax-ws.dev.java.net) for basic Web services, industry de-facto JAXB (http://jaxb.dev.java.net) for data binding and WS-* specs and proven interoperability with .NET 3.0 framework using WSIT (http://wsit.dev.java.net).

stanquinn - Aug 30, 2007 - 06:49 PM
Post subject: nice....guess that means no Salesforce Web Clients

I'm building a Salesforce Web Client (API 10.0) and all the documentation is for Axis. Pisser.

tomeksz - Sep 25, 2007 - 03:54 PM
Post subject: RE: nice....guess that means no Salesforce Web Clients

But this doesn't mean that you can't use it with XFire :)

gnkr - Oct 19, 2007 - 10:18 PM
Post subject:

Doest the new Myeclips6.0 has support for Axis2 and is it easy to do develpoments using that.

support-rkalla - Oct 22, 2007 - 03:19 PM
Post subject:

Quote:

Doest the new Myeclips6.0 has support for Axis2 and is it easy to do develpoments using that.

No, we don't support Axis2 at this time.