Tag: swagger

Posted on

Swagger-Jaxb 1.8 released

Small update, forgot to inform you.

As the title states. I released swagger-jaxb 1.8.

The changes are community made and

  • refactor the code for easier use with https://github.com/icellmobilsoft/openapi-jaxb
  • document usage with gradle

Posted on

Released Swagger JAXB Plugin

It maybe 4 years overdue, but thanks to issue 7 on swagger-jaxb I have finally released swagger-jaxb 1.5 into Maven Central.  You can now all use it in your favourite build tool that supports m2 repositories, or build it yourself from the repository. ( That is, if you use Java 8 )

swagger-jaxb is a jaxb plugin that adds @ApiModel and @ApiModelProperty to your generated classes. You could use it with the jaxb2-maven-plugin, see the repo for information.

You may also report issues on the github repo

Posted on

Swagger JAXB

JAXB XJC Plugin for automatically adding annotations from Swagger to generated classes from an XSD. I’ve created this when I noticed that for very complex schemas when there are references that stack the Swagger UI Javascript gave Stackoverflow errors, adding the annotations manually to the generated classes fixed it. But: you don’t want to change generated code huh! Thus swagger-jaxb emerged from the need to add swagger annotations automatically.

Please note this plugin is in development phase !! Currently only available with maven through the sonatype snapshot repositories. It is not complete and there are some open issues, but you can already use it.

Is all going well ?

Tests run in separate project, but do they work ? see here for the code https://github.com/redlab/swagger-jaxb-tck

How to use it?

  • build the plugin with maven and install it in your local repo or get it from an external repo like sonatypes snapshot repository
  • add the plugin to your classpath and use -swaggify on your jaxb command line or use it with jaxb2-maven-plugin
<plugin>
        <groupId>org.codehaus.mojo</groupId>
        <artifactId>jaxb2-maven-plugin</artifactId>
        <version>1.5</version>
        <executions>
                <execution>
                <id>internal.generate</id>
                <goals>
                    <goal>xjc</goal>
                </goals>
                <configuration>
                    <arguments>-swaggerify</arguments>
                    <clearOutputDir>true</clearOutputDir>
                    <schemaDirectory>${project.basedir}/src/main/resources/xsd//api</schemaDirectory>
                    <packageName>com.example.api.model</packageName>
                    <staleFile>${project.build.directory}/generated-sources/jaxb/.api.internal</staleFile>
                </configuration>
            </execution>
        </executions>
        <dependencies>
            <dependency>
                <groupId>javax.xml.parsers</groupId>
                <artifactId>jaxp-api</artifactId>
                <version>1.4.5</version>
            </dependency>
            <dependency>
                <groupId>com.sun.xml.parsers</groupId>
                <artifactId>jaxp-ri</artifactId>
                <version>1.4.5</version>
            </dependency>
            <dependency>
                <groupId>com.sun.xml.bind</groupId>
                <artifactId>jaxb-xjc</artifactId>
                <version>2.2.7-b53</version>
            </dependency>
            <dependency>
                <groupId>com.sun.xml.bind</groupId>
                <artifactId>jaxb-impl</artifactId>
                <version>2.2.7-b53</version>
            </dependency>
            <dependency>
                <groupId>be.redlab.jaxb</groupId>
                <artifactId>swagger-jaxb</artifactId>
                <version>0.0.1-SNAPSHOT</version>
            </dependency>
        </dependencies>
    </plugin>

The plugin dependencies are needed until the JAXB2 plugin is updated to use the latest version of jaxb-xjc and jaxp. Otherwise the code generation will fail due to missing methods. Note: I think this will change the generated code for boolean getters/setters, not fully sure I must verify it to be sure 🙂

post an issue at github if you really want dev version in Maven Central.