Defaults for Options don't appear to be supported about dropwizard-scala

[nicktelford]

This definitely sounds like a problem I'd like to resolve, however I'm having some trouble reproducing it.

Would you mind adding a test that demonstrates the issue, perferably to ScalaApplicationSpecIT, but if you can't stomach that mass of code, a standalone test would be fine too.

Ideally, it should fail, I imagine with a 'NullPointerException, or other reason that clearly demonstrates the default beingnull`.

FWIW, Scala's optional arguments will never work with Jersey, as it's completely unaware of them. The Jersey way to define defaults for an argument is to use the @DefaultValue(...) annotation on the argument. However, this is for customising a default argument for your code, and it definitely makes sense that Option should default to None, instead of null.

[nicktelford]

Could you also confirm the version of both Scala and dropwizard-scala that you're using?

[zbelzer]

Thanks for responding. I'm just trying to maintain the status quo while switching libraries here. Somehow defaults were supported before, so I'm curious as to whether or not I'm crazy or something bigger changed.

I have a PR with a couple tests, fwiw, but it sounds like this is working as expected per your comments above #7

[nicktelford]

Yeah, so your tests pretty much confirm what I said above. I'm not sure how Scala's default arguments can ever have worked in Jersey, given the way they compile.

I'm afraid that, since this is the expected behaviour, there's nothing I can really do about it. Your best bet would be to use @DefaultValue(Some(...)) instead of Scala's default arguments. Not ideal, but then Jersey doesn't exactly integrate great with Scala anyway.