Comments on: BlazeDS, AMF and read only properties

By: cornel

cornel — Wed, 16 Dec 2009 09:26:42 +0000

Acnesiac,

The dataservice object should have one instance per destination. It’s not ok to have two of them.

By: acnesiac

acnesiac — Tue, 24 Nov 2009 20:07:28 +0000

Hello i got a question, if i have two instance of the same dataservices, pointing to the same destination, why if i change the collection asocciated to one ds, the flag commitrequired is set to true in both dataservices?

best regards

By: cornel

cornel — Mon, 21 Sep 2009 20:54:59 +0000

Hi Simeon,

Thanks for your comment. When I’ll have time i will dig on GraniteDS.
Related to performance, do you have some quick number?
Another thing: hessian (caucho implementation) is also much faster than amf3 serialization (from blazeds) however I discovered some edge cases where hessian were not able to serialize efficient at all. It would be nice to do a comparison with GraniteDS also in terms of robustness.

By: Simeon

Simeon — Mon, 21 Sep 2009 20:46:32 +0000

We were working with BlazeDS and ran into some serialization issues. Some having to do with AS Number NaN being converted to a Double as 0. I dug into the code and found that it was easy to fix going into blazeDS but nearly impossible to fix on the reverse serialization.

In order to not have to go through our some odd 40 VO classes and implement our own custom serialization we actually took a look at GrantiteDS. GraniteDS actually has the ability to add an annotation to your class and it will implement the custom serialization pieces on your class at compile time. Then as an added feature you can actually generate the ActionScript VO’s from those java classes using their tool. Which allowed us to implement custom serialization without spending a week writing the code.

Another pleasant surprise was that we found granite to work much faster than Blaze. That was not something we had planned for but was a nice bonus after the switch.

Just tossing out an item for consideration.