Support for dropwizard v0.8 series about dropwizard-swagger HOT 5 CLOSED

I forked this repo, dropwizard-junit, and dropwizard-swagger-sample-app and updated each of them to use the current development snapshot of dropwizard-0.8. There were a few bumps along the way, but I got the basic cases demonstrated in the sample app working. However, in order to build a dropwizard-swagger artifact, I had to make an adjustment to the test that probably should not be accepted in a pull request. Also, the selenium tests are still failing. See carltonwhitehead@d8cac4e

from dropwizard-swagger.

Hi @carltonwhitehead
Is there a way to work around the above exception trace? My project depends on dw 0.8 but I hoped to take advantage of swagger "auto-magically", sad to realize the magic is broken...

from dropwizard-swagger.

I ran into the same issue. You can get around this by including the dependency on the latest version of dropwizard-views-freemarker

For example, if you're using gradle you can modify the build.gradle file and include as a dependency:

compile "io.dropwizard:dropwizard-views-freemarker:[your version of dw - 0.8.0X]"

from dropwizard-swagger.

Is just including new latest freemarker enough, though? The original problem above has to do with classes declared in the dropwizard-views package. You'd need the latest of that to fix the problem, and when you get that imported you get this issue:

Exception in thread "main" java.lang.InstantiationError: io.dropwizard.views.ViewBundle
    at io.federecio.dropwizard.swagger.SwaggerDropwizard.onInitialize(SwaggerDropwizard.java:47)
    at com.actian.dataflood.service.DFApplication.initialize(DFApplication.java:51)
    at io.dropwizard.Application.run(Application.java:71)
    at com.actian.dataflood.service.DFApplication.main(DFApplication.java:36)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:483)
    at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)

because of the ViewBundle being abstract. If the ViewBundle were in a separate package you might be able to do dependency magic, but you need the latest views dependency. Fixes appear to be required to use this with 0.8.0.

On that note, mins ago on #37 @vultron81 submitted a pull request for this...

from dropwizard-swagger.

Dropwizard 0.8 is now supported in version 0.6 which has just been deployed to Maven Central and the README has been updated accordingly (@vultron81 and @thiagomoretto both submitted pull requests).

from dropwizard-swagger.