[Jaxrs-Resteasy] Improvements for Jaxrs-Resteasy

[jfiala]

Description

The generated code stubs are way to complicated, in fact only the following files are needed for Resteasy (verified with Jboss EAP 7):

• Api-Interface (with all JaxRS-annotations)
• Implementation class implementing the interface
• Class to activate Jax-RS: @ApplicationPath / extends RestApplication

Additional Fixes

• the api is generated as class, but IMHO this should be an interface!?
• @ApiResponse are missing

this has already been fixed in the master branch

• @Api annotation is missing (see [JAX-RS RESTEasy] Generated JAX-RS RESTEasy stub is missing swagger annotations #4447)

this has already been fixed in #4447

• create deployable WAR file (see Can't generate a deployable war when using jaxrs-resteasy #4461)

The current state of #4712 allows to generate a simple structure with interfaces holding all JaxRS-annotations and a simple implementation class. Registration for JaxRS is done by extending Jaxrs Application. It has been verified to work for Jboss EAP 6 + 7 as no resteasy-specific libraries are included ( resteasy-jackson2-provider is now provided as opposed to jaxrs-resteasy).

Datetime-Support

• joda datetime support (using configuration of Jackson ObjectMapper)
• java8 datetime support (using configuration of Jackson ObjectMapper)

This language supports Java8 and Joda datetime using the JacksonConfig, the needed dependencies included automatically (see pom.mustache).

I added the flag "joda" to AbstractJavaCodegen.java to allow checking for joda in the mustache templates.

Further Enhancements

• javax.ws.rs.core.Response is used instead of the real response data type

should better be changed separately see #4713

• optional: activate Swagger contract generator (ApiListingResource / SwaggerSerializers)

Questions

• SecurityContext should be better removed from method signatures to have a clean interface
  (see https://github.com/swagger-api/swagger-core/wiki/Swagger-Core-RESTEasy-2.X-Project-Setup-1.5)

Swagger-codegen version

2.2.2-SNAPSHOT

Related issues

#4447 regarding the Swagger annotations
#4461 regarding WAR-file
#4123 for enums
#3446 for tag support

Suggest a Fix

If you like, I can provide a new simplified Resteasy language.
Using the dynamic Swagger contract generator it provides true turnaround development...

[mbucc]

@jfiala What do you think about putting the EAP version in the language name? For example, renaming jaxrs-resteasy to jaxrs-reasteasy-eap7? RestEasy 3 (and other libs in pom) are not included in EAP6, so jaxrs-resteasy did not build for me out of the box.

[jfiala]

@mbucc I think this would be a good starting point, as I worked only with EAP 7 here, this way we can also target for 2.2.2.
Later if we can warrant backwards compatibility somehow for EAP 6 we can then replace jaxrs-resteasy (for 2.3).

I'd add a new language jaxrs-resteasy-eap7 and wouldn't change the existing jaxrs-resteasy in the first place.

@wing328 what do you think?

[mbucc]

@jfiala FWIW, you can rename existing jaxrs-resteasy if you like. It will not work with eap6.

[jfiala]

@mbucc for which Resteasy/Jboss version was the current implementation supposed for?
I'd like to greatly simplify the generated files as there are only interfaces/models and one initialization class needed to work with Jboss EAP 7.

[mbucc]

@jfiala here is my understanding: existing jaxrs-resteasy codegen only works for EAP 7.

• the pom uses resteasy 3 (https://github.com/swagger-api/swagger-codegen/blob/master/modules/swagger-codegen/src/main/resources/JavaJaxRS/resteasy/pom.mustache#L164)

• EAP 6 provides resteasy 2 (https://access.redhat.com/articles/112673.)

• the generated code fails to compile if you downgrade rest easyversion in pom.mustache

Note that the servlet api version could be upgraded as well; 2.5 was last used in EAP 5: (https://access.redhat.com/articles/113373)

I can contribute files for eap 6, assuming I can get past the ApiResponse issue I opened in #4617.

[mbucc]

@jfiala I just realized something. Resteasy is a stand alone library, so I suspect the author built this codegen for that scenario.

At work, I use JBoss container, which provides RestEasy, so I was only thinking about this codegen in context of JBoss. But there are other containers where the war artifact built here will work just fine.

Sorry for the diversion!

(Seems like I should simply create a jboss6-resteasy codegen based on this one. Sound reasonable to you?)

[jfiala]

@mbucc OK, thx for the clarification. I'd like to provide the first draft with name resteasy-jboss and I'll test it for both jboss 6 and 7 eap (better put language first, then target jee server). In the next step/release 2.3, we could replace the existing resteasy language.
It would be great if you can give it a test run, we can then also check how to fix your issue #4617.

[jfiala]

@mbucc I added a first re-implementation of Jaxrs Resteasy in PR #4712, please take a look when you have time.

I added all resteasy dependencies (also resteasy-jackson2-provider) as provided, so it doesn't depend on a specific resteasy version. I verified it to deploy on Jboss EAP 6 + 7 without errors.