Java开发网 - about XFire

Topic: about XFire

1.about XFire

Posted by: lcwling
Posted on: 2006-04-26 22:51

最近时间要写一些ＷｅｂＳｅｒｖｉｃｅ，看到Ｘｆｉｒｅ好像有替代Ａｘｉｓ之势，不知道各位做如何评价？

http://xfire.codehaus.org/
http://xfire.codehaus.org/XFire+1.0-RC1+Release+Notes

Codehaus XFire is a next-generation java SOAP framework. Codehaus XFire makes service oriented development approachable through its easy to use API and support for standards. It is also highly performant since it is built on a low memory StAX based model.

2.Re:about XFire [Re: lcwling]	Copy to clipboard
Posted by: zcjl Posted on: 2006-04-27 09:58 看过一些demo，Easily Embedded 和 Easily Create Services from POJOs 这两个feature感觉很不错，Easily integrated with Spring也是目前流行的趋势。JAXB 2.0 and XMLBeans Support这两个不知道会有什么好处。基本上，目前我还是喜欢xml configuration 胜于 annotation，所以JSR181 Support也不太习惯

3.Re:about XFire [Re: lcwling]	Copy to clipboard
Posted by: YuLimin Posted on: 2006-05-07 11:20 没用过，速度、性能如何呢？对复杂对象，附件支持如何呢？有没有与AXIS的对比有何优势？

4.Re:about XFire -- 1.1.1 Release [Re: lcwling]

Copy to clipboard

Posted by: why
Posted on: 2006-06-21 01:47

XFire 1.1.1 Release (June 18, 2006)
http://xfire.codehaus.org/XFire+1.1.1+Release+Notes

> 有没有与AXIS的对比有何优势？
http://netzooid.com/blog/2005/10/31/15-to-20-transactions-a-second-try-xfire/
(from http://xfire.codehaus.org/Performance )
a couple of the highlights:
* 25-85 messages a second
* 2-6 times as faster as Axis 1.3
* 1/2-1/5 the latency of Axis 1.3

http://docs.codehaus.org/display/XFIRE/2005/11/20/XFire+Performance+Results+from+Tim+Pokorny

5.Re:about XFire [Re: lcwling]	Copy to clipboard
Posted by: jacshan Posted on: 2006-07-11 11:33 现在不是出来axis2了吗?不知道好好用

6.Re:about XFire [Re: lcwling]	Copy to clipboard
Posted by: 鬼浪仔 Posted on: 2006-07-17 10:40 版主漂亮

7.XFire 1.1.2 Released [Re: lcwling]	Copy to clipboard
Posted by: lcwling Posted on: 2006-07-17 23:25 Jun 25, 2006 XFire 1.1.2 Released! http://xfire.codehaus.org/XFire+1.1.2+Release+Notes XFire 1.1.2 incorporates several bug fixes since 1.1.1: Fix compilation issues with client and JAXB examples DOM mode namespace bug fix Fix minor JAX-WS fault name generation

8.Re:about XFire [Re: lcwling]

Copy to clipboard

Posted by: lcwling
Posted on: 2006-07-17 23:39

目前,要设计一个并发性和实时性要求较高的应用,也一直在考虑采用WebSerive还是直接采用Socket编程,由于对性能要求比较高,而WebService是用牺牲性能来换取跨平台的远程过程调用或者消息交换的。由于采用了SOAP这样的标准协议，用XML序列化，而非二进制,两者可能有1个数量级的差距。

Xfire也素以excellent performance标示,实在没有精力将两者一一实现,进行比对,到底性能如何,希望做过这方面的CJSDER,能够指点一二...或者有没有其他的解决方案.

TIA!

9.Re:about XFire [Re: lcwling]

Copy to clipboard

Posted by: floater
Posted on: 2006-07-18 04:23

I would try webservice first. If it's slow then switch to socket. If it's pojo based design, you should be able to reuse pojo.

use jbuilder or axis tools or spring, your webservice coding should be minimal.
I trained folks before with jbuilder, in 2 hours they can get the wrappers done.

Haven't tried XFire before, but switching implementations should not be a big operation, otherwise there is a design problem, which is a bigger problem.

Have you tried axis 2?

10.Re:about XFire [Re: lcwling]	Copy to clipboard
Posted by: lcwling Posted on: 2006-07-19 20:39 Thanks,floater.以前用过axis 1.X,后来用IBM中间件将java class包装成webservice or ejb,其实只要pojo设计的好,的确,用什么server实现起来都不需要花太多的功夫.但如果用socket编程的话,并发连接数该怎么控制合适一些?

11.Re:about XFire [Re: lcwling]	Copy to clipboard
Posted by: doumingjunniit Posted on: 2006-08-05 11:03 XFIRE是一种免费的框架,他可以实现不同服务器之间的数据传输,并且配置也相当简单,不象EJB实现远程调用那么复杂.