Remove Outdated Quickstarts

Description: The app-client quickstart demonstrates how to code and package a client app and use the WildFly/JBoss EAP client container to start the client Main program.

Removal justification: We should not be encouraging the use of this outdated technology. Besides that it’s not Openshift compatible and achieving that would not be practical.

Description: The bean-validation quickstart provides Arquillian tests to demonstrate how to use CDI, JPA, and Bean Validation.

Removal justification: The bean-validation-custom-constraint quickstart is better and we don’t need two quickstarts with respect to Bean Validation.

Description: The ejb-asynchronous quickstart demonstrates the behavior of asynchronous EJB invocations by a deployed EJB and a remote client and how to handle errors.

Removal justification: We have too many EJB related quickstarts, and we don’t feel this one provides enough value to keep. The asynchronous EJB functionality usage makes little sense, and besides that, this quickstart is not Openshift compatible.

Description: The ejb-in-ear quickstart demonstrates how to deploy an EAR archive that contains a JSF WAR and an EJB JAR.

Removal justification: We have too many EJB related quickstarts, and we don’t feel this one provides enough value to keep. The ejb-throws-exception quickstart covers the same basic EJB usage, and a bit more.

Description: The ejb-in-war quickstart demonstrates how to package an EJB bean in a WAR archive and deploy it to WildFly/JBoss EAP. Arquillian tests are also provided.

Removal justification: We have too many EJB related quickstarts, and we don’t feel this one provides enough value to keep. The ejb-throws-exception quickstart covers the same basic EJB usage, and a bit more.

Description: The ejb-security quickstart demonstrates the use of Jakarta EE declarative security to control access to EJBs in WildFly/JBoss EAP.

Removal justification: The concept of securing EJBs is still relevant but we have other quickstarts providing that, and this particular quickstart does not show anything useful on the server side, because the required configuration is now present in the out of the box configuration.

Description: The ejb-security-jaas quickstart demonstrates how legacy JAAS security domains can be used in conjunction with Elytron

Removal justification: This quickstart is no longer relevant since it involved configuring a legacy security domain and delegating authentication and authorization decisions to this legacy domain. We should instead look at introducing a new quickstart that covers the new jaas-realm Elytron resource.

Description: The greeter quickstart demonstrates the use of CDI, JPA, JTA, EJB and JSF in WildFly/JBoss EAP.

Removal justification: This quickstart just shows technologies well covered by many other quickstarts, and thus we feel it’s redundant and should be removed.

Description: The helloworld-html5 quickstart demonstrates the use of CDI 1.2 and JAX-RS 2.0 using the HTML5 architecture and RESTful services on the backend.

Removal justification: This quickstart is just a REST helloworld variant, which uses HTML5 too. We believe that the jaxrs-client quickstart is better as a basic REST quickstart, and it’s enough to just keep that one.

Description: The helloworld-mbean quickstart demonstrates the use of CDI and MBean in WildFly/JBoss EAP and includes JConsole instructions and Arquillian tests.

Removal justification: Usage of MBeans on apps is no longer a feature we want to promote, it’s outdated and it’s not Openshift friendly.

Description: The helloworld-rs quickstart demonstrates a simple Hello World application, bundled and deployed as a WAR, that uses JAX-RS to say Hello.

Removal justification: This quickstart is just a REST helloworld variant. We believe that the jaxrs-client quickstart is better as a basic REST quickstart, and it’s enough to just keep that one.

Description: The helloworld-ssl quickstart is a basic example that demonstrates server side SSL configuration in WildFly/JBoss EAP.

Removal justification: The out of the box configuration already contains a key-store, key-manager, server-ssl-context and the Undertow https-listener is already configured to make use of this server-ssl-context. So this quickstart doesn’t actually demonstrate anything useful at this point.

Description: The inter-app quickstart shows you how to use a shared API JAR and an EJB to provide inter-application communication between two WAR deployments.

Removal justification: The functionality demonstrated by this quickstart is proprietary, not cloud friendly, and thus we feel this quickstart is not worth to keep.

Description: The jaxws-addressing quickstart is a working example of the web service using WS-Addressing.

Removal justification: We only need two basic quickstarts regarding JAXWS, one about the most common Annotations usage, and another one with respect to the alternative usage of WSDL and we feel that the jaxws-ejb and jaxws-retail are the ones we should keep.

Description: The jaxws-pojo quickstart is a working example of the web service endpoint created from a POJO.

Removal justification: We only need two basic quickstarts regarding JAXWS, one about the most common Annotations usage, and another one with respect to the alternative usage of WSDL and we feel that the jaxws-ejb and jaxws-retail are the ones we should keep.

Description: The jts-distributed-crash-rec quickstart uses JTS and Byteman to demonstrate distributed crash recovery across multiple application servers.

Removal justification: This quickstart is outdated and is not Openshift compatible, we feel this is worth the effort to fix and keep.

Description: The kitchensink-angularjs quickstart demonstrates a Jakarta EE application using AngularJS with JAX-RS, CDI, EJB, JPA, and Bean Validation.

Removal justification: This quickstart just adds an angularjs frontend to the standard kitchensink quickstart, which is not worth to keep considering the focus on the Developer Guide.

Description: The kitchensink-ear quickstart demonstrates web-enabled database application, using JSF, CDI, EJB, JPA, and Bean Validation, packaged as an EAR.

Removal justification: This quickstart just changes the application packaging type compared to the standard kitchensink quickstart, which is not worth to keep considering the focus on the Developer Guide.

Description: The kitchensink-jsp quickstart demonstrates how to use JSP, JSTL, CDI, EJB, JPA, and Bean Validation in WildFly/JBoss EAP.

Removal justification: This quickstart just adds JSP to the standard kitchensink quickstart, which is not worth to keep considering the focus on the Developer Guide.

Description: The kitchensink-ml quickstart demonstrates a localized Jakarta EE compliant application using JSF, CDI, EJB, JPA, and Bean Validation.

Removal justification: This quickstart just adds localization to the standard kitchensink quickstart, which we will move to the standard quickstart.

Description: The logging-tools quickstart shows how to use JBoss Logging Tools to create internationalized loggers, exceptions, and messages and localize them.

Removal justification: This quickstart is redundant, the logging qukckstarts is better with respect to logging, and kitchensink covers better the localization functionality.

Description: The managed-executor-service quickstart demonstrates how Jakarta EE applications can submit tasks for asynchronous execution.

Removal justification: The thread-racing quickstart is more complete yet simpler demonstration of the usage of Concurrency Utilities, no need to keep this one too.

Description: The messaging-clustering quickstart does not contain any code and instead uses the helloworld-mdb quickstart to demonstrate clustering using ActiveMQ Messaging.

Removal justification: This is just a doc and CLI scripts with different way to use helloworld-mdb, we should move the doc content to the developer guide and move the CLI scripts to helloworld-mdb, no need to keep this on its own.

Description: The payment-cdi-event quickstart demonstrates how to create credit and debit CDI Events in WildFly/JBoss EAP, using a JSF front-end client.

Removal justification: This quickstart is redundant, considering basic CDI usage on many other quickstarts we will keep. Also the CDI component lead want to focus in the future in showing more advanced CDI usage on new/upgraded quickstarts.

Description: The resteasy-jaxrs-client quickstart demonstrates an external JAX-RS RestEasy client, which interacts with a JAX-RS Web service that uses CDI and JAX-RS.

Removal justification: This quickstart is just a client to use with the helloworld-rs quickstart, and we believe that the jaxrs-client quickstart is better as a basic REST quickstart, and it’s enough to just keep that one.

Description: The spring-greeter quickstart is based on the greeter quickstart, but differs in that it uses Spring MVC for Mapping GET and POST requests.

Removal justification: We just need one Spring related quickstart, and the spring-resteasy one is the best one to keep.

Description: The spring-kitchensink-basic quickstart is an example of a Jakarta EE application using JSP, JPA and Spring 5.x.

Removal justification: We just need one Spring related quickstart, and the spring-resteasy one is the best one to keep.

Description: The spring-kitchensink-springmvctest quickstart demonstrates how to create an MVC application using JSP, JPA and Spring 5.x.

Removal justification: We just need one Spring related quickstart, and the spring-resteasy one is the best one to keep.

Description: The tasks-rs quickstart demonstrates how to implement a JAX-RS service that uses JPA persistence.

Removal justification: This quickstart is a JAXRS variant of the tasks-jsf quickstart, which (unlike this one) is OpenShift compatible and we will keep.

Description: Demonstrates use of a Javascript WebSocket client, WebSocket configuration, programmatic binding, and secure WebSocket.

Removal justification: This quickstart is redundant considering the websocket functionality covered, we will keep just the websocket-hello and websocket-endpoint quickstarts.

Description: The xml-jaxp quickstart demonstrates how to use Servlet and JSF to upload an XML file to WildFly/JBoss EAP and validate and parse it using DOM or SAX.

Removal justification: The topics covered by this quickstart are not really related with WildFly/EAP, and not worth to cover in developer guide (file upload, xml parsing).