Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-17289

Deliver a set of Quickstarts which showcase WildFly major enhancements wrt provisioning, cloud and testing




      • The Quickstarts to deliver with WildFly 28, showcasing major enhancements, should:
        • Cover WildFly main functional areas, such as Web apps, Web Services/REST, Database/JPA, Messaging and EJBs.
        • Be compatible with OpenShift.
      • The following WildFly Cloud/Provisioning/Testing enhancements should be delivered by all selected Quickstarts:
        • Provisioning
          • The WildFly Maven Plugin is now capable of provisioning a server with specific features (through Galleon layers), configure it using CLI scripts, and package it with an application deployed. Each selected Quickstart should demonstrate how to use this new WildFly Maven Plugin functionality to provision a server with the needed Galleon layers, configure it using a CLI script if required, and package it with Quickstart’s application deployed.
        • Cloud
          • Helm charts may be used to build and deploy an application on OpenShift, with improved user experience compared with the previous S2i usage. Each selected Quickstart should demonstrate how to use Helm Charts to build and deploy the Quickstart’s application on OpenShift.
        • Testing
          • The Quickstarts should demonstrate how users may test their applications with WildFly, on baremetal and OpenShift environments. The delivered Quickstarts should include integration tests, abstract from the environment where the server is running, and take advantage of Arquillian and the other Quickstarts enhancements to run such tests.
            • On standard server distribution the traditional commands should be used to build and deploy the Quickstart, and use the Arquillan remote container to run the tests.
            • On provisioned server the WildFly Maven Plugin should be used to locally provision the server with the application deployed, and use the Arquillan managed container to run the tests.
            • On OpenShift the Helm Charts should be used to build and deploy the server with the application, and use Arquillian remote container to run the tests.
      • The following Quickstarts were reviewed by the developer team and selected for being delivered with the enhancements:
        • cmt
          • Main WildFly functionality covered: Transactions, Messaging
        • Ee-security
          Main WildFly functionality covered: EE Security
        • Helloworld
          Main WildFly functionality covered: Servlets
        • Helloworld-ws
          Main WildFly functionality covered: Web Services
        • Jaxrs-client
          Main WildFly functionality covered: REST
        • Kitchensink
          Main WildFly functionality covered: Multiple (JSF, CDI, EJB, JPA, and Bean Validation)
        • Numberguess
          Main WildFly functionality covered: CDI, JSF
        • Servlet-security
          Main WildFly functionality covered: Servlet, Elytron
        • Temperatureconverter
          Main WildFly functionality covered: EJB
        • Thread-racing
          Main WildFly functionality covered: Batch, EE Concurrency, Messaging, REST
        • Todo-backend
          Main WildFly functionality covered: Datasource, Openshift
        • Websocket-hello
          Main WildFly functionality covered: Web Socket




            emartins@redhat.com Eduardo Martins
            emartins@redhat.com Eduardo Martins
            0 Vote for this issue
            2 Start watching this issue