update tests to run with both JSON and XML

Is this done? If not, is it required for 1.0, which we're hoping to announce tomorrow?

this isn't done, but isn't critical for release

(from [aa08bebf52b18782998d5fe7c5c29e98f8625f5f]) [#40 bug in deserializing CamelCase in FromXMLDelegate] handle multi word class names , [#23 update tests to run with both JSON and XML] added unit tests for json and xml serialization and deserialization. Improved serialization of NSNumber , added a way to format NSDate serialization http://github.com/yfactorial/obj...

the only big difference between rails xml and ours when serializing is nil objects don't create <element type="type" nil="true"> just <element>

rollback the isEqualToRemote fix? We honestly should pick either NSString or NSNumber for the id and stick with that. And all the methods expect a NSString so the easiest thing to do would be to use NSString for now

I mean comment out this: http://github.com/yfactorial/obj...

until 1.1 and the test that breaks because of it.

For 1.1 we really need to switch to NSNumber, since that's what Rails provides by default.

(from [7164876628f8184bd00639dcd4b0371b26da3cc3]) [#23 update tests to run with both JSON and XML] remove number support http://github.com/yfactorial/obj...

(from [0321b10a18a157f6169977c5aa91ed7344b460d0]) [#45 cleanup Person properties] cleaned up person , [#23 update tests to run with both JSON and XML] OS update http://github.com/yfactorial/obj...