{"issue":{"created_at":"2011-12-06T01:21:32Z","state":"open","updated_at":"2011-12-06T01:21:32Z","comments":0,"user":{"gravatar_id":"9b197571b0eb5e2fbfaf2cee5afabc8a","id":14872,"url":"https://api.github.com/users/apetresc","login":"apetresc","avatar_url":"https://secure.gravatar.com/avatar/9b197571b0eb5e2fbfaf2cee5afabc8a?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"body":"I've written a simple Kryo serializer for twitter4j.Status objects, which simply uses JSON, [posted here](https://gist.github.com/1436239). I register this serializer with Storm at runtime:\r\n\r\n    \t\tconfig.setFallBackOnJavaSerialization(false);\r\n\t\tconfig.registerSerialization(Status.class, Twitter4JStatusCustomSerializer.class);\r\n\r\nHowever, this causes Storm to [fail during initialization](https://gist.github.com/1436144) in a very mysterious way. Notice that the stack trace doesn't include my code at all. However, if I remove those two lines above (and therefore let it fall back on default serialization), everything works, so I can only assume the serializer registration is causing the issue.","assignee":null,"id":2457372,"number":64,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"labels":[],"title":"Storm fails on initialization when defining a custom serializer","html_url":"https://github.com/nathanmarz/storm/issues/64","closed_at":null,"url":"https://api.github.com/repos/nathanmarz/storm/issues/64","milestone":null},"action":"opened"}