Well, the first problem I can see is that it is not clear how a synchronized class should behave. It is not defined anywhere. If you try to come up with a definition of your own, you might soon get into some trouble (what about static methods, public fields, public static fields etc.)
Secondly, it might not benefit you much. The most naive interpretation of a "synchronized class" is rather easily doable in Java: just make every non-private method synchronized and every non-final field private. In my experience you usually want more sophisticated design, therefore the real use of this "synchronized class" would be very limited anyway.
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop