BlazeDS vs. GraniteDS [英] BlazeDS vs. GraniteDS

问题描述

任何人都有评估BlazeDS和GraniteDS的经验吗？我很好奇在与Spring / Hibernate集成方面哪个更好。

解决方案

如果您只是在寻找简单的RPC和消息，我会和Blaze一起去的。这些实现更加成熟和更好地证明了，特别是在消息方面。花岗岩的消息是基于彗星，从我记忆中还是很新的。更多细节如下...

Blaze DS基本上是一个包含RPC和一些HTTP简单消息服务的栈。使用FlexFactory的SpringFactory实现可以轻松实现与Spring的集成：只需在Google类名称中找到代码即可。它不提供任何额外的支持与Hibernate相关的东西。

花岗岩DS在特性方面正在快速增长。它与LCDS比Blaze DS更多。它包括解析Hibernate对象图并以干净的方式处理懒惰代理的能力。他们还有一个名为Tide的工具，在Flex客户端中创建Session的模拟，以确保实体的唯一性。他们也明确支持通过Spring，EJB3和Seam公开的服务。花岗岩也有一个从你的Java类生成AS3类的实用程序（虽然这不难写，如果你想自己）。

大约一年前，我曾与花岗岩并有一些问题得到它正确解析对象图; Flash Player会抛出一些讨厌的低级异常。我的猜测是，文档和实现已经成熟，因此这些已不再是问题。不过，我仍然有点犹豫，推荐它，因为我遇到了问题，切换到Blaze立即解决他们没有任何麻烦。

Anyone have any experience evaluating BlazeDS and GraniteDS? I'm curious about which is better at integrating with Spring/Hibernate.

解决方案

If you are just looking for simple RPC and messaging, I would go with Blaze. The implementations are more mature and better proven, especially with respect to messaging. The messaging in Granite is based on Comet and still pretty new from what I remember. More details below...

Blaze DS is basically a stack that includes RPC and some simple messaging services over HTTP. Integration with Spring is achieved easily using the SpringFactory implementation of FlexFactory: just google the class name and you'll find the code. It doesn't offer any additional support for things Hibernate-related.

Granite DS is growing rapidly in terms of features. It competes more with LCDS than Blaze DS. It includes the ability to parse Hibernate object graphs and deal with lazy proxies in a clean fashion. They also have a tool called "Tide" that creates an analog of a Session in the Flex client to ensure uniqueness of entities. They also have explicit support for services exposed via Spring, EJB3 and Seam. Granite also has a utility for generating AS3 classes from your Java classes (although this not hard to write yourself if you want to).

I worked with Granite about a year ago and had some problems getting it properly parse object graphs; the Flash Player would throw some nasty low-level exceptions. My guess is that the documentation and implementation have matured since so that these are no longer issues. However, I'm still a bit hesitant to recommend it since I ran into issues and switching to Blaze immediately resolved them with no trouble at all.

这篇关于BlazeDS vs. GraniteDS的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！