Axis1.x->Axis2的最重要特征是:
hot deployment(Axis2 addresses技术)
hot update
但我个人却对hot deployment/update不感冒,因此我仍然抱着XFire不放.
很多人都认为AXIS2是垃圾代码产物, 打开AXIS2的Team页:http://ws.apache.org/axis2/team-list.html
,你发现WSO2几乎主导了整个AXIS2设计, WSO2据说是一个斯里兰卡的公司, AXIS2好多都是由学生式代码堆砌的, 可以用非常烂来形容.
http://www.jroller.com/page/fate?entry=axis2_why_bother
有些人被Apache的不纯洁感到忧虑, WTO2的主导者Davanum Srinivas本身是一个顾问, 他是否想通过AXIS2获取更多的顾问费, 不得而知了.
用江南白衣的话来形容AXIS2, "那是一点都不POJO,不Spring!"
最后, 看看Denis Robert是如何批斗AXIS2的:
另外, TSS的AXIS2讨论也非常激烈:
http://www.theserverside.com/news/thread.tss?thread_id=40280
hot deployment(Axis2 addresses技术)
hot update
但我个人却对hot deployment/update不感冒,因此我仍然抱着XFire不放.
很多人都认为AXIS2是垃圾代码产物, 打开AXIS2的Team页:http://ws.apache.org/axis2/team-list.html
,你发现WSO2几乎主导了整个AXIS2设计, WSO2据说是一个斯里兰卡的公司, AXIS2好多都是由学生式代码堆砌的, 可以用非常烂来形容.
http://www.jroller.com/page/fate?entry=axis2_why_bother
有些人被Apache的不纯洁感到忧虑, WTO2的主导者Davanum Srinivas本身是一个顾问, 他是否想通过AXIS2获取更多的顾问费, 不得而知了.
用江南白衣的话来形容AXIS2, "那是一点都不POJO,不Spring!"
最后, 看看Denis Robert是如何批斗AXIS2的:
No question about it, stick with XFire. You’ll be
happy about it. My only gripe with XFire is the docs,
which are woefully incomplete. Hopefully that will
change with time. For the time being, you have to
plow through the source for any complex service.
But architecturally, it’s really sound.
Axis2 is a nightmare. Even with XFire’s incomplete
docs, I was able to go through the source to figure
out what I needed. Axis2 is such a jumble of code that
doing the same thing would take weeks, not hours.
Also, compared to Axis2, XFire’s docs are positively
brilliant! Not only are Axis2’s docs fragmentary
at best, half of it doesn’t correpond to the current
version.
XFire looks like it’s going in the right direction,
and Dan Diephouse (the lead) seems like he’s on top
of the project.
You also have to take JAX-WS into account. Whether or
not it’s all it’s cracked up to be is another
discussion, but it nevertheless is the official standard.
The Axis2 team have made clear that they have
no intention of supporting it. JAX-RPC was horrible,
but it was at least common ground, and was the API
used by most enterprise users. Same will end up happening
with JAX-WS and JAXB 2. Websphere users will
end up using that, and knowing it’s out there will
make interop a lot easier. XFire has taken a “can’t
beat ‘em, join ‘em” approach here.
The way I see it, the Axis team dropped the ball on
this one, and the new kid has taken the lead.
It’s the circle of life…
happy about it. My only gripe with XFire is the docs,
which are woefully incomplete. Hopefully that will
change with time. For the time being, you have to
plow through the source for any complex service.
But architecturally, it’s really sound.
Axis2 is a nightmare. Even with XFire’s incomplete
docs, I was able to go through the source to figure
out what I needed. Axis2 is such a jumble of code that
doing the same thing would take weeks, not hours.
Also, compared to Axis2, XFire’s docs are positively
brilliant! Not only are Axis2’s docs fragmentary
at best, half of it doesn’t correpond to the current
version.
XFire looks like it’s going in the right direction,
and Dan Diephouse (the lead) seems like he’s on top
of the project.
You also have to take JAX-WS into account. Whether or
not it’s all it’s cracked up to be is another
discussion, but it nevertheless is the official standard.
The Axis2 team have made clear that they have
no intention of supporting it. JAX-RPC was horrible,
but it was at least common ground, and was the API
used by most enterprise users. Same will end up happening
with JAX-WS and JAXB 2. Websphere users will
end up using that, and knowing it’s out there will
make interop a lot easier. XFire has taken a “can’t
beat ‘em, join ‘em” approach here.
The way I see it, the Axis team dropped the ball on
this one, and the new kid has taken the lead.
It’s the circle of life…
另外, TSS的AXIS2讨论也非常激烈:
http://www.theserverside.com/news/thread.tss?thread_id=40280
