No differentiation between inner class names

We use a lot of static inner classes as a way of grouping together similar, but not identical dtos. For example:

public class CustomerDto {
  public static class In {
    // fields for saving a new customer
  }
  public static class Out {
    // fields returned when querying a customer.
  }
}

  public class Address {
    public static class In {
      //...
    }

    public static class Out {
      //...
    }
  }

In this case, it looks like the swagger.json is including only one of the In classes (with the reference “#/definitions/In”) and one of the Out classes.

This makes it fairly unusable since the apis using the other In/Out classes have the wrong model.

At the least, could the generation fail if it gets naming conflicts? Right now it’s just silently referencing the wrong model.

I’m using Jersey to generate the swagger.json if that helps/makes a difference.

Thanks.

[PavelJ]

I have just encountered this behaviour and was really suprised because I would assume that this would be a serious issue. For example I have one User model and have multiple request and response classes for multiple operations with User - each containing only a subset of User’s attributes.

For example I have class CreateUserRequest (in one package) annotated with @JsonRootName(value = “user”) and another class UpdateUsersStateRequest (may be even in the same package) again with annotation @JsonRootName(value = “user”). Swagger definition has only one of those definitions and ignoring others so basically most of the generated examples which I see in swagger UI are wrong.

I would assume that swagger would have different definition for each REST method, am I missing something? It is extremely important to be able to define same object with different attributes in different API methods.

[frantuma]

A solution for this issue has been implemented in #2797, check out this comment and related test case, to be able to customize name resolving