Changing of the Guard: AXIS out, JAXWS in

re: Changing of the Guard: AXIS out, JAXWS in

Jason Kilgrow — Thu, 31 Jul 2008 16:40:36 GMT

"Fifty nine jar files? Really? Do I need this hassle?"

My sentiment EXACTLY!! Thank you! It's so nice to know that I'm not the only one who is FED UP with the crap that is Axis2.

I maintain a few Axis web services and they seem to be in good shape. But I am tired of the circus that Axis2 has become.

If web services are all about interoperability, maybe the Axis2 team needs to go back and remember that themselves. I can't get any client except an Axis2 client to talk to an Axis2 service. Maybe it's me...maybe it's the service...but maybe, just maybe, it's Axis2.

re: Changing of the Guard: AXIS out, JAXWS in

Harel — Sun, 03 Aug 2008 08:31:34 GMT

"Fifty nine jar files"

The large number of jar files is a result of using Maven and breaking the functionality into smaller components.

(They can just as well toss it all into a one big jar file)

It's true that Axis2 is a bit bloated if you just need the core web services, but I prefer their maven driven component approach design as opposed to monolithic design.

btw, I am using Axis2 in a production environment with various clients consuming it.

http://blogs.sun.com/theaquarium/entry/metro_90_better_performing_than

TrackBack — Mon, 04 Aug 2008 20:58:45 GMT

http://blogs.sun.com/arungupta/entry/why_glassfish_metro_over_axis

TrackBack — Mon, 04 Aug 2008 20:58:58 GMT

re: Changing of the Guard: AXIS out, JAXWS in

DotNetInterop — Mon, 04 Aug 2008 22:26:24 GMT

I'm sure that AXIS2 is being used, and I'm glad you're getting a good experience out of it.

Isn't there a major problem with the entire philosophy of Maven and the implications of independently versioned subcomponents? There are too many moving parts, too many versioned components. The test matrix is huge.

When AXIOM or JAXB or XMLbeans or etc etc gets updated, how does one go and verify that everything is still working properly?

It's Jar Hell, which I've written about before.

If the idea is that the 59 jars from AXIS will not be shared by any other system (thereby avoiding most of Jar Hell) , then it really SHOULD be a single monolithic jar.

Just my opinion. I'm not an Apache member, I just use the stuff.