[jersey-dev] jersey heroku archetype fix

[back Button <back.button@xxxxxxx>]

The fix is in the web.xml for the archetype.

Only after setting  metadata-complete="false"

can both Jettys be used.

The embedded Jetty and the Maven Jetty archetype.

Please look into the effects of metadata-complete="false" or metadata-complete="true"

The  FAULTY archetype found here in eclipse documentation

https://eclipse-ee4j.github.io/jersey.github.io/documentation/latest3x/getting-started.html#deploy-it-on-heroku

mvn archetype:generate -DarchetypeArtifactId=jersey-heroku-webapp \

                -DarchetypeGroupId=org.glassfish.jersey.archetypes -DinteractiveMode=false \

                -DgroupId=com.example -DartifactId=simple-heroku-webapp -Dpackage=com.example \

                -DarchetypeVersion=3.0.1




<!--web.xml -->

<?xml version="1.0" encoding="UTF-8"?>

<web-app xmlns="https://jakarta.ee/xml/ns/jakartaee";
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
    xsi:schemaLocation="https://jakarta.ee/xml/ns/jakartaee
                      https://jakarta.ee/xml/ns/jakartaee/web-app_5_0.xsd";
    metadata-complete="false" version="5.0">

    <servlet>
        <servlet-name>Jersey Web Application</servlet-name>
        <servlet-class>org.glassfish.jersey.servlet.ServletContainer</servlet-class>
        <init-param>
            <param-name>jersey.config.server.provider.packages</param-name>
            <param-value>com.example</param-value>
        </init-param>
        <load-on-startup>1</load-on-startup>
    </servlet>

    <servlet-mapping>
        <servlet-name>Jersey Web Application</servlet-name>
        <url-pattern>/api/*</url-pattern>
    </servlet-mapping>

    <welcome-file-list>
        <welcome-file>main.jsp</welcome-file>
    </welcome-file-list>

</web-app>

https://lit-taiga-52898.herokuapp.com/

back.button@xxxxxxx