Anton Kropp
Anton Kropp
Any traction on this? This is pretty annoying
Yeah a websocket factory would be nice. I think that's more useful than a url factory
Can we merge this?
As a temporary workaround I disabled anyval support in my application and to get the json to be over the wire the same I added the `@(JsonValue @getter)` annotation to...
You can do ``` protected val jsonMapper = new JsonMethods { val m = objectMapper.registerModule(new Json4sScalaModule) override def mapper: ObjectMapper = { m } } ``` Then you can basically...
Is this fixed for scala 2.10? This is a big nuisance
Are there any workarounds to this?
@lure I'm not sure what you mean? So you can't use an anyval in an option?
I see, thanks for that. Unfortunately, I can't really repo this local and I am seeing this in production. I'd rather not enable this in production, is there no information...
I was able to find the error in verbose mode, but for what its worth it would be much more helpful from an integration standpoint to just throw the error...