We have a project where we created some domain classes using 1.1.0.M1. We got rid of the persistence as we are not interested in this feature. We liked that Roo gives us a kind of live code generation for things like getters and setters, etc. Those classes only have @RooJavaBean, @RooSerializable and/or @RooToString at the moment, depending on our needs.
However, when we upgraded to 1.1.0.M3, classes annotated with @RooJavaBean started to get Json serialization/deserialization, which we didn't asked for. We think json support shouldn't be linked to this annotation. If this was the intended behaviour, then we think one should be able to exclude json by providing certain flags in the annotation (enhancement)... otherwise this is a bug (unintended feature
Background thread in forum: http://forum.springsource.org/showthread.php?p=321478#post321478