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
