A devfile is a file that describes and define a development environment:+
diff --git a/README.adoc b/README.adoc
deleted file mode 100644
index 56610722aa..0000000000
--- a/README.adoc
+++ /dev/null
@@ -1,679 +0,0 @@
-//***********************************************************************************
-// Enable the following flag to build README.html files for JBoss EAP product builds.
-// Comment it out for WildFly builds.
-//***********************************************************************************
-:ProductRelease:
-
-//***********************************************************************************
-// Enable the following flag to build README.html files for EAP CD product builds.
-// Comment it out for WildFly or JBoss EAP product builds.
-//***********************************************************************************
-//:EAPCDRelease:
-
-//***********************************************************************************
-// Enable the following flag to build README.html files for EAP XP product builds.
-// Comment it out for WildFly or JBoss EAP product builds.
-//***********************************************************************************
-//:EAPXPRelease:
-
-// This is a universal name for all releases
-:ProductShortName: JBoss EAP
-// Product names and links are dependent on whether it is a product release (CD or JBoss)
-// or the WildFly project.
-// The "DocInfo*" attributes are used to build the book links to the product documentation
-
-ifdef::ProductRelease[]
-// JBoss EAP release
-:productName: JBoss EAP
-:productNameFull: Red Hat JBoss Enterprise Application Platform
-:productVersion: 7.4
-:DocInfoProductNumber: {productVersion}
-
-endif::[]
-
-ifdef::EAPXPRelease[]
-// JBoss EAP XP release
-:productName: JBoss EAP XP
-:productNameFull: Red Hat JBoss Enterprise Application Platform expansion pack
-:productVersion: 2.0
-:DocInfoProductNumber: 7.3
-endif::[]
-
-ifdef::ProductRelease,EAPXPRelease[]
-:githubRepoUrl: https://github.com/jboss-developer/jboss-eap-quickstarts/
-:jbossHomeName: EAP_HOME
-:DocInfoProductName: Red Hat JBoss Enterprise Application Platform
-:DocInfoProductNameURL: red_hat_jboss_enterprise_application_platform
-:DocInfoPreviousProductName: jboss-enterprise-application-platform
-:quickstartDownloadName: {productNameFull} {productVersion} Quickstarts
-:quickstartDownloadUrl: https://access.redhat.com/jbossnetwork/restricted/listSoftware.html?product=appplatform&downloadType=distributions
-// END ifdef::ProductRelease,EAPXPRelease[]
-endif::[]
-
-ifndef::ProductRelease,EAPCDRelease,EAPXPRelease[]
-// WildFly project
-:productName: WildFly
-:productNameFull: WildFly Application Server
-:jbossHomeName: WILDFLY_HOME
-:productVersion: 23
-:githubRepoUrl: https://github.com/wildfly/quickstart/
-:DocInfoProductName: Red Hat JBoss Enterprise Application Platform
-:DocInfoProductNameURL: red_hat_jboss_enterprise_application_platform
-// Do not update the following until after the 7.4 docs are published!
-:DocInfoProductNumber: 7.3
-:DocInfoPreviousProductName: jboss-enterprise-application-platform
-// END ifndef::ProductRelease,EAPCDRelease,EAPXPRelease[]
-endif::[]
-
-:source: {githubRepoUrl}
-
-// Values for Openshift S2i sections attributes
-:CDProductName: {productNameFull} for OpenShift
-:CDProductShortName: {ProductShortName} for OpenShift
-:CDProductTitle: {CDProductName}
-:CDProductNameSentence: Openshift release for {ProductShortName}
-:CDProductAcronym: {CDProductShortName}
-:CDProductVersion: {productVersion}
-:EapForOpenshiftBookName: {productNameFull} for OpenShift
-:EapForOpenshiftOnlineBookName: {EapForOpenshiftBookName} Online
-:xpaasproduct: {productNameFull} for OpenShift
-:xpaasproductOpenShiftOnline: {xpaasproduct} Online
-:xpaasproduct-shortname: {CDProductShortName}
-:xpaasproductOpenShiftOnline-shortname: {xpaasproduct-shortname} Online
-:ContainerRegistryName: Red Hat Container Registry
-:EapForOpenshiftBookName: Getting Started with {ProductShortName} for OpenShift Container Platform
-:EapForOpenshiftOnlineBookName: Getting Started with {ProductShortName} for OpenShift Online
-:OpenShiftOnlinePlatformName: Red Hat OpenShift Container Platform
-:OpenShiftOnlineName: Red Hat OpenShift Online
-:ImagePrefixVersion: eap74-beta
-:ImageandTemplateImportURL: https://raw.githubusercontent.com/jboss-container-images/jboss-eap-openshift-templates/{ImagePrefixVersion}/
-
-// OpenShift repository and reference for quickstarts
-:EAPQuickStartRepo: https://github.com/jboss-developer/jboss-eap-quickstarts
-:EAPQuickStartRepoRef: 7.4.x
-// Links to the OpenShift documentation
-:LinkOpenShiftGuide: https://access.redhat.com/documentation/en-us/{DocInfoProductNameURL}/{DocInfoProductNumber}/html-single/getting_started_with_jboss_eap_for_openshift_container_platform/
-:LinkOpenShiftOnlineGuide: https://access.redhat.com/documentation/en-us/{DocInfoProductNameURL}/{DocInfoProductNumber}/html-single/getting_started_with_jboss_eap_for_openshift_online/
-
-ifdef::EAPCDRelease[]
-// Attributes for EAP CD release
-:CDProductName: JBoss Enterprise Application Platform continuous delivery
-:CDProductShortName: {ProductShortName} Continuous Delivery
-:CDProductTitle: JBoss Enterprise Application Platform Continuous Delivery
-:CDProductNameSentence: continuous delivery release for {ProductShortName}
-:CDProductAcronym: JBoss EAP CD
-:CDProductVersion: 21
-:productName: {CDProductShortName}
-:productNameFull: {CDProductName}
-:productVersion: {CDProductVersion}
-:githubRepoUrl: https://github.com/jboss-developer/jboss-eap-quickstarts/tree/openshift/
-:DocInfoProductNameURL: jboss_enterprise_application_platform_continuous_delivery
-:DocInfoProductName: JBoss Enterprise Application Platform Continuous Delivery
-:DocInfoProductNumber: {productVersion}
-:quickstartDownloadName: JBoss EAP CD {productVersion} Quickstarts
-:quickstartDownloadUrl: https://access.redhat.com/jbossnetwork/restricted/listSoftware.html?product=eap-cd&downloadType=distributions
-// OpenShift repository and reference for quickstarts
-:EAPQuickStartRepoRef: openshift
-// END ifdef::EAPCDRelease[]
-endif::[]
-
-ifdef::EAPXPRelease[]
-// Attributes for XP releases
-:EapForOpenshiftBookName: {productNameFull} for OpenShift
-:EapForOpenshiftOnlineBookName: {productNameFull} for OpenShift Online
-:xpaasproduct: {productNameFull} for OpenShift
-:xpaasproductOpenShiftOnline: {productNameFull} for OpenShift Online
-:xpaasproduct-shortname: {ProductShortName} for OpenShift
-:xpaasproductOpenShiftOnline-shortname: {ProductShortName} for OpenShift Online
-:ContainerRegistryName: Red Hat Container Registry
-:EapForOpenshiftBookName: {productNameFull} for OpenShift
-:EapForOpenshiftOnlineBookName: {productNameFull} for OpenShift Online
-:ImagePrefixVersion: eap-xp2
-:ImageandTemplateImportURL: https://raw.githubusercontent.com/jboss-container-images/jboss-eap-openshift-templates/{ImagePrefixVersion}/
-// OpenShift repository and reference for quickstarts
-:EAPQuickStartRepoRef: xp-2.0.x
-// Links to the OpenShift documentation
-:LinkOpenShiftGuide: https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/{DocInfoProductNumber}/html/using_eclipse_microprofile_in_jboss_eap/using-the-openshift-image-for-jboss-eap-xp_default
-:LinkOpenShiftOnlineGuide: https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/{DocInfoProductNumber}/html/using_eclipse_microprofile_in_jboss_eap/using-the-openshift-image-for-jboss-eap-xp_default
-endif::[]
-
-//*************************
-// Other values
-//*************************
-:buildRequirements: Java 8.0 (Java SDK 1.8) or later and Maven 3.3.1 or later
-:jbdsEapServerName: Red Hat JBoss Enterprise Application Platform 7.3
-:javaVersion: Jakarta EE 8
-ifdef::EAPXPRelease[]
-:javaVersion: Eclipse MicroProfile
-endif::[]
-:githubRepoBranch: master
-:guidesBaseUrl: https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/
-:useEclipseUrl: {guidesBaseUrl}USE_JBDS.adoc#use_red_hat_jboss_developer_studio_or_eclipse_to_run_the_quickstarts
-:useEclipseDeployJavaClientDocUrl: {guidesBaseUrl}USE_JBDS.adoc#deploy_and_undeploy_a_quickstart_containing_server_and_java_client_projects
-:useEclipseDeployEARDocUrl: {guidesBaseUrl}USE_JBDS.adoc#deploy_and_undeploy_a_quickstart_ear_project
-:useProductHomeDocUrl: {guidesBaseUrl}USE_OF_{jbossHomeName}.adoc#use_of_product_home_and_jboss_home_variables
-:configureMavenDocUrl: {guidesBaseUrl}CONFIGURE_MAVEN_JBOSS_EAP.adoc#configure_maven_to_build_and_deploy_the_quickstarts
-:arquillianTestsDocUrl: {guidesBaseUrl}RUN_ARQUILLIAN_TESTS.adoc#run_the_arquillian_tests
-:addUserDocUrl: {guidesBaseUrl}CREATE_USERS.adoc#create_users_required_by_the_quickstarts
-:addApplicationUserDocUrl: {guidesBaseUrl}CREATE_USERS.adoc#add_an_application_user
-:addManagementUserDocUrl: {guidesBaseUrl}CREATE_USERS.adoc#add_an_management_user
-:startServerDocUrl: {guidesBaseUrl}START_JBOSS_EAP.adoc#start_the_jboss_eap_server
-:configurePostgresDocUrl: {guidesBaseUrl}CONFIGURE_POSTGRESQL_JBOSS_EAP.adoc#configure_the_postgresql_database_for_use_with_the_quickstarts
-:configurePostgresDownloadDocUrl: {guidesBaseUrl}CONFIGURE_POSTGRESQL_JBOSS_EAP.adoc#download_and_install_postgresql
-:configurePostgresCreateUserDocUrl: {guidesBaseUrl}CONFIGURE_POSTGRESQL_JBOSS_EAP.adoc#create_a_database_user
-:configurePostgresAddModuleDocUrl: {guidesBaseUrl}CONFIGURE_POSTGRESQL_JBOSS_EAP.adoc#add_the_postgres_module_to_the_jboss_eap_server
-:configurePostgresDriverDocUrl: {guidesBaseUrl}CONFIGURE_POSTGRESQL_JBOSS_EAP.adoc#configure_the_postgresql_driver_in_the_jboss_eap_server
-:configureBytementDownloadDocUrl: {guidesBaseUrl}CONFIGURE_BYTEMAN.adoc#download_and_configure_byteman
-:configureBytemanDisableDocUrl: {guidesBaseUrl}CONFIGURE_BYTEMAN.adoc#disable_the_byteman_script
-:configureBytemanClearDocUrl: {guidesBaseUrl}CONFIGURE_BYTEMAN.adoc#clear_the_transaction_object_store
-:configureBytemanQuickstartDocUrl: {guidesBaseUrl}CONFIGURE_BYTEMAN.adoc#configure_byteman_for_use_with_the_quickstarts
-:configureBytemanHaltDocUrl: {guidesBaseUrl}CONFIGURE_BYTEMAN.adoc#use_byteman_to_halt_the_application[
-:configureBytemanQuickstartsDocUrl: {guidesBaseUrl}CONFIGURE_BYTEMAN.adoc#configure_byteman_for_use_with_the_quickstarts
-
-:EESubsystemNamespace: urn:jboss:domain:ee:4.0
-:IiopOpenJdkSubsystemNamespace: urn:jboss:domain:iiop-openjdk:2.0
-:MailSubsystemNamespace: urn:jboss:domain:mail:3.0
-:SingletonSubsystemNamespace: urn:jboss:domain:singleton:1.0
-:TransactionsSubsystemNamespace: urn:jboss:domain:transactions:4.0
-
-// LinkProductDocHome: https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/
-:LinkProductDocHome: https://access.redhat.com/documentation/en/jboss-enterprise-application-platform-continuous-delivery
-:LinkConfigGuide: https://access.redhat.com/documentation/en-us/{DocInfoProductNameURL}/{DocInfoProductNumber}/html-single/configuration_guide/
-:LinkDevelopmentGuide: https://access.redhat.com/documentation/en-us/{DocInfoProductNameURL}/{DocInfoProductNumber}/html-single/development_guide/
-:LinkGettingStartedGuide: https://access.redhat.com/documentation/en-us/{DocInfoProductNameURL}/{DocInfoProductNumber}/html-single/getting_started_guide/
-:LinkOpenShiftWelcome: https://docs.openshift.com/online/welcome/index.html
-:LinkOpenShiftSignup: https://docs.openshift.com/online/getting_started/choose_a_plan.html
-:OpenShiftTemplateName: JBoss EAP CD (no https)
-
-:ConfigBookName: Configuration Guide
-:DevelopmentBookName: Development Guide
-:GettingStartedBookName: Getting Started Guide
-
-:JBDSProductName: Red Hat CodeReady Studio
-:JBDSVersion: 12.15
-:LinkJBDSInstall: https://access.redhat.com/documentation/en-us/red_hat_codeready_studio/{JBDSVersion}/html-single/installation_guide/
-:JBDSInstallBookName: Installation Guide
-:LinkJBDSGettingStarted: https://access.redhat.com/documentation/en-us/red_hat_codeready_studio/{JBDSVersion}/html-single/getting_started_with_codeready_studio_tools/
-:JBDSGettingStartedBookName: Getting Started with CodeReady Studio Tools
-
-:outfilesuffix: .html
-
-:toc:
-:toclevels: 4
-:numbered:
-
-ifndef::ProductRelease,EAPCDRelease,EAPXPRelease[]
-= WildFly Quickstarts
-
-[toc]
-
-[abstract]
-The quickstarts demonstrate Jakarta EE 8 and a few additional technologies from the WildFly stack. They provide small, specific, working examples that can be used as a reference for your own project.
-
-[[introduction]]
-== Introduction
-
-These quickstarts run on the WildFly application server. The quickstarts are configured to use the correct Maven dependencies and ensure that you test and compile the quickstarts against the correct runtime environment.
-
-Each quickstart folder contains a `README.adoc` file that describes the quickstart features and provides instructions about how to build and run it. Instructions are provided to build the more readable `README.html` files.
-
-Make sure you read this entire document before you attempt to work with the quickstarts.
-
-[[system_requirements]]
-== System Requirements
-
-The applications these projects produce are designed to be run on WildFly 16 or later.
-
-All you need to build these projects is Java 8.0 (Java SDK 1.8) or later and Maven 3.3.1 or later.
-
-[[use_of_product_home_and_jboss_home_variables]]
-== Use of WILDFLY_HOME and QUICKSTART_HOME Variables
-
-The quickstart `README` files use the _replaceable_ value `__WILDFLY_HOME__` to denote the path to the WildFly server. When you encounter this value in a `README` file, make sure you replace it with the actual path to your WildFly server.
-
-When you see the replaceable variable __QUICKSTART_HOME__, replace it with the path to the root directory of all of the quickstarts.
-
-[[prerequisites]]
-== Prerequisites
-
-Before you begin, you must perform the following tasks.
-
-. xref:build_wildfly_server[Build the WildFly Server (Optional)]: This step is only required if you plan to run the latest https://github.com/wildfly/wildfly[development version of the WildFly server]. It is not required if you are running a https://github.com/wildfly/wildfly/tags[tagged] or https://github.com/wildfly/wildfly/releases[released] version of the WildFly server.
-
-. xref:build_wildfly_boms[Build and Install the WildFly BOMs (Optional)]: This step is only required if you are building a development version of the WildFly server and see dependency issues when you build the quickstarts. It is not required if you are running a https://github.com/wildfly/quickstart/tags[tagged] or https://github.com/wildfly/boms/releases[released] version of the WildFly server.
-
-. xref:install_the_quickstart_parent_artifact_in_maven[Install the Quickstart Parent Artifact in Maven (Optional)]: This step is only required if you are running the latest https://github.com/wildfly/quickstart[development version of the quickstarts]. It is not required if you are running a https://github.com/wildfly/quickstart/tags[tagged] or https://github.com/wildfly/quickstart/releases[released] version of the quickstarts.
-
-. xref:build_quickstart_readme_files[Build the Quickstart README.html Files (Required)]: The quickstart `README` files are written in AsciiDoc to provide modular, reusable content; however, this makes them difficult to read. For this reason, you must also build the quickstart `README.html` files from the AsciiDoc source.
-
-[[build_wildfly_server]]
-=== Build the WildFly Server (Optional)
-
-If you have downloaded a https://github.com/wildfly/wildfly/tags[tagged] or https://github.com/wildfly/wildfly/releases[released] version of the WildFly server, you can ignore this step. You can simply extract the WildFly server from the compressed file and https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/START_JBOSS_EAP.adoc#start-the-red-hat-jboss-enterprise-application-platform-server[start the server] from that directory.
-
-If you plan to run the https://github.com/wildfly/wildfly[development version of the WildFly server], you must first download and build the WildFly server from source.
-
-. If you have not yet done so, you must clone https://github.com/wildfly/wildfly[WildFly server] repository and navigate to it. You might also want to change the remote name from `origin` to `upstream` to be consistent with your other repositories.
-+
-[source,options="nowrap"]
-----
-$ git clone git@github.com:wildfly/wildfly.git
-$ cd wildfly
-$ git remote rename origin upstream
-----
-. Verify that your local `master` branch contains the latest updates.
-+
-[source,options="nowrap"]
-----
-$ git fetch upstream
-$ git checkout master
-$ git reset --hard upstream/master
-----
-
-. Build the WildFly server using the following command.
-+
-[source,options="nowrap"]
-----
-$ mvn clean install -DskipTests -Denforcer.skip=true -Dcheckstyle.skip=true
-----
-
-. The WildFly server folder and ZIP files, which are named `wildfly-__VERSION__-SNAPSHOT` and `wildfly-__VERSION__-SNAPSHOT.ZIP` respectively, are located in the `build/target/` directory. You can copy that folder or unzip the file to another location or https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/START_JBOSS_EAP.adoc#start-the-red-hat-jboss-enterprise-application-platform-server[start the server] from that directory.
-
-
-[[build_wildfly_boms]]
-=== Build and Install the WildFly BOMs (Optional)
-
-If you have downloaded and are running a https://github.com/wildfly/quickstart/tags[tagged] or https://github.com/wildfly/quickstart/releases[released] version of the quickstarts, you can ignore this step because the required BOMs are already installed in Maven.
-
-If you are using the latest https://github.com/wildfly/quickstart[development version] of the quickstarts and you are able to successfully build and deploy the quickstarts, you can also ignore this step because the required BOMS are already installed in Maven.
-
-However, if you are using the latest https://github.com/wildfly/quickstart[development version] of the quickstarts and you see build errors indicating missing dependencies, you must first xref:build_wildfly_server[build the latest WildFly server] and then build and install the WildFly BOMs. This installs the latest Maven artifacts that are required by the SNAPSHOT version of the WildFly quickstarts that are still under development.
-
-. If you have not yet done so, clone https://github.com/wildfly/boms[WildFly BOMs] repository and navigate to it. You might also want to rename the directory to `wildfly-boms` to make it clear which BOMs it contains and also change the remote name from `origin` to `upstream` to be consistent with your other repositories.
-+
-[source,options="nowrap"]
-----
-$ git clone git@github.com:wildfly/boms.git
-$ mv boms wildfly-boms
-$ cd wildfly-boms
-$ git remote rename origin upstream
-----
-. Verify that your local `master` branch contains the latest updates.
-+
-[source,options="nowrap"]
-----
-$ git fetch upstream
-$ git checkout master
-$ git reset --hard upstream/master
-----
-
-. Build the WildFly BOMs using the following command.
-+
-[source,options="nowrap"]
-----
-$ mvn clean install
-----
-+
-NOTE: If you run into build errors, check with the WildFly team to see if the repositories are temporarily out of sync.
-
-. At this point, you can verify that all of the quickstarts build using the following command.
-+
-[source,options="nowrap"]
-----
-$ mvn clean install '-Pdefault,!complex-dependencies'
-----
-
-[[install_the_quickstart_parent_artifact_in_maven]]
-=== Install the Quickstart Parent Artifact in Maven (Optional)
-
-The root `POM.xml` file defines dependencies that are required by some of the quickstarts.
-
-If you have downloaded and are running a https://github.com/wildfly/quickstart/tags[tagged] or https://github.com/wildfly/quickstart/releases[released] version of the quickstarts, you can ignore this step because the `quickstart-parent` artifact is already installed in Maven.
-
-If you are running the latest https://github.com/wildfly/quickstart[development version] of the quickstarts, you must install the `quickstart-parent` artifact so its dependencies are available to the quickstarts that need it. To install it, navigate to your __QUICKSTART_HOME__ directory directory and run the following command.
-
-[source,subs="+quotes,attributes+",options="nowrap"]
-----
-$ cd __QUICKSTART_HOME__
-$ mvn clean install -N
-----
-
-[[build_quickstart_readme_files]]
-=== Build the Quickstart README.html Files (Required)
-
-The quickstart `README` files are written in AsciiDoc, not only because the language is much more powerful than Markdown, but also also because it is possible to extract common instructions into separate files to be reused across the quickstarts. While this makes them more flexible and easier to maintain, unfortunately, included files do not render in a readable format in GitHub or in most text editors.
-
-The Maven plugin that is used to build and deploy the quickstarts can also generate fully rendered `README.html` instructions from the `README.adoc` files.
-
-To build all of the quickstart `README.html` files, including the root `README.html` file that contains the table with links to all available quickstarts, navigate to the root folder of the quickstarts and run the following command.
-
-[source,options="nowrap"]
-----
-$ mvn clean package -Pdocs
-----
-
-[TIP]
-====
-To build the `README.html` file for a specific quickstart, navigate to the quickstart directory and run the above command.
-====
-
-If you see errors about missing dependencies, check the xref:prerequisites[prerequisites] section to determine whether you need to xref:build_wildfly_boms[build the WildFly BOMs] that corresponds to the version of the quickstarts that you are using.
-
-[[suggested_approach_to_the_quickstarts]]
-== Suggested Approach to the Quickstarts
-
-We recommend that you approach the quickstarts as follows:
-
-* Regardless of your level of expertise, we suggest you start with the `helloworld` quickstart. It is the simplest example and is an easy way to prove the server is configured and running correctly.
-* If you are a beginner or new to JBoss, start with the quickstarts labeled `Beginner`, then try those marked as `Intermediate`. When you are comfortable with those, move on to the `Advanced` quickstarts.
-* Some quickstarts are based upon other quickstarts but have expanded capabilities and functionality. If a prerequisite quickstart is listed, make sure you deploy and test it before looking at the expanded version.
-
-
-[[run_the_quickstarts]]
-== Run the Quickstarts Using the Maven Command Line
-
-The root folder of each individual quickstart contains a `README.html` file with detailed instructions on how to build and run the example. In most cases you do the following:
-
-* https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/START_JBOSS_EAP.adoc#start_the_jboss_eap_server[Start the WildFly server].
-* Optionally, you can xref:build_the_quickstart_archive[build the quickstart archive] to test for compile errors.
-* xref:build_and_deploy_the_quickstart[Build and deploy the quickstart].
-* xref:undeploy_the_quickstart[Undeploy the quickstart] when you are finished testing.
-
-IMPORTANT: See the `README` file in each individual quickstart folder for specific details and information on how to run and access the example.
-
-[[build_the_quickstart_archive]]
-=== Build the Quickstart Archive
-
-You can follow these steps to build the application to test for compile errors or to view the contents of the archive. See the specific quickstart `README` file for complete details.
-
-. Open a terminal and navigate to the root directory of the quickstart you want to build.
-. Use the following command if you only want to build the archive, but not deploy it.
-+
-[source,options="nowrap"]
-----
-$ mvn clean install
-----
-
-[[build_and_deploy_the_quickstart]]
-=== Build and Deploy the Quickstart
-
-This section describes the basic steps to build and deploy an application. See the specific instructions in each quickstart `README` file for any variations to this process.
-
-. Make sure you start the WildFly server as described in the quickstart `README` file.
-. Open a terminal and navigate to the root directory of the quickstart you want to run.
-. Use the following command to build and deploy the archive.
-+
-[source,options="nowrap"]
-----
-$ mvn clean install wildfly:deploy
-----
-
-[[undeploy_the_quickstart]]
-=== Undeploy the Quickstart
-
-Use the following command to undeploy the quickstart.
-
-[source,options="nowrap"]
-----
-$ mvn wildfly:undeploy
-----
-
-[[run_the_quickstarts_in_jboss_developer_studio_or_eclipse]]
-== Run the Quickstarts in Red Hat CodeReady Studio or Eclipse
-
-You can also start the server and deploy the quickstarts or run the Arquillian tests from Eclipse using JBoss tools. For general information about how to import a quickstart, add a WildFly server, and build and deploy a quickstart, see https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/USE_JBDS.adoc#use_red_hat_jboss_developer_studio_or_eclipse_to_run_the_quickstarts[Use Red Hat CodeReady Studio or Eclipse to Run the Quickstarts].
-
-[[optional_components]]
-== Configure Optional Components
-
-The following components are needed for only a small subset of the quickstarts. Do not install or configure them unless the quickstart requires it.
-
-* xref:create_quickstart_users[Create Quickstart Users]
-* xref:configure_postgresql[Configure the PostgreSQL Database]
-* xref:configure_byteman[Configure Byteman]
-
-[[create_quickstart_users]]
-=== Create Quickstart Users
-
-Some of the quickstarts, particularly those that run in a secured mode and demonstrate security, require that you create quickstart users with different roles for authorization purposes. See https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CREATE_USERS.adoc#create_users_required_by_the_quickstarts[Create Users Required by the Quickstarts] for detailed instructions to create users required by the quickstarts.
-
-[[configure_postgresql]]
-=== Configure the PostgreSQL Database
-
-Some of the quickstarts that demonstrate transactions require that you install and configure the PostgreSQL database. See https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_POSTGRESQL_JBOSS_EAP.adoc#configure_the_postgresql_database_for_use_with_the_quickstarts[Configure the PostgreSQL Database for Use with the Quickstarts] for instructions.
-
-[[configure_byteman]]
-=== Configure Byteman
-
-A few of the quickstarts use _Byteman_ to demonstrate distributed transaction processing and crash recovery. See https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_BYTEMAN.adoc#configure_byteman_for_use_with_the_quickstarts[Configure Byteman for Use with the Quickstarts] for instructions.
-
-// END ifndef::ProductRelease,EAPCDRelease,EAPXPRelease[]
-endif::[]
-
-//**********************************************************************************
-//
-// WildFly Developers: You can ignore the rest of this file.
-// It is for the JBoss EAP product and XP Releases.
-//
-//**********************************************************************************
-
-ifdef::ProductRelease,EAPXPRelease[]
-// These instructions are only for the JBoss EAP product and XP Releases.
-= {productNameFull} ({productName}) Quickstarts
-
-[abstract]
-The quickstarts demonstrate {javaVersion} and a few additional technologies from the {productNameFull} stack. They provide small, specific, working examples that can be used as a reference for your own project.
-
-[[introduction]]
-== Introduction
-
-These quickstarts run on {productNameFull} {productVersion}. Each quickstart folder contains a `README.html` file that describes the quickstart features and provides instructions about how to build and run it.
-
-We recommend that you use the *{quickstartDownloadName}* ZIP file, which you can download from the {quickstartDownloadUrl}[{productName} Software Download] page on the Red Hat Customer Portal. This version of the quickstarts uses the correct dependencies and ensures that you test and compile against the correct server runtime environment.
-
-Each quickstart folder contains a `README.html` file that describes the quickstart features and provides instructions about how to build and run it.
-
-Make sure you read this entire document before you attempt to work with the quickstarts.
-
-[[system_requirements]]
-== System Requirements
-
-The applications these projects produce are designed to be run on {productNameFull} {productVersion} or later.
-
-All you need to build these projects is {buildRequirements}.
-
-[[use_of_product_home_and_jboss_home_variables]]
-== Use of {jbossHomeName} and QUICKSTART_HOME Variables
-
-The quickstart `README` files use the _replaceable_ value `__{jbossHomeName}__` to denote the path to the {productName} installation. When you encounter this value in a `README` file, make sure you replace it with the actual path to your {productName} installation. The installation path is described in detail here: link:{useProductHomeDocUrl}[Use of __{jbossHomeName}__ and __JBOSS_HOME__ Variables]
-
-When you see the replaceable variable __QUICKSTART_HOME__, replace it with the path to the root directory of all of the quickstarts.
-
-[[suggested_approach_to_the_quickstarts]]
-== Suggested Approach to the Quickstarts
-
-We suggest you approach the quickstarts as follows:
-
-* Regardless of your level of expertise, we suggest you start with the `helloworld` quickstart. It is the simplest example and is an easy way to prove the server is configured and running correctly.
-* If you are a beginner or new to JBoss, start with the quickstarts labeled `Beginner`, then try those marked as `Intermediate`. When you are comfortable with those, move on to the `Advanced` quickstarts.
-* Some quickstarts are based upon other quickstarts but have expanded capabilities and functionality. If a prerequisite quickstart is listed, make sure you deploy and test it before looking at the expanded version.
-
-[[run_the_quickstarts]]
-== Run the Quickstarts Using the Maven Command Line
-
-The root folder of each individual quickstart contains a `README` file with specific details on how to build and run the example. In most cases you do the following:
-
-* link:{StartServerDocUrl}[Start the {productName} server].
-* Optionally, you can xref:build_the_quickstart_archive[build the quickstart archive] to test for compile errors.
-* xref:build_and_deploy_the_quickstart[Build and deploy the quickstart].
-* xref:undeploy_the_quickstart[Undeploy the quickstart] when you are finished testing.
-
-IMPORTANT: See the `README` file in each individual quickstart folder for specific details and information on how to run and access the example.
-
-[[build_the_quickstart_archive]]
-==== Build the Quickstart Archive
-
-You can follow these steps to build the application to test for compile errors or to view the contents of the archive. See the specific quickstart `README` file for complete details.
-
-. Open a terminal and navigate to the root directory of the quickstart you want to build.
-. Use the following command if you only want to build the archive, but not deploy it.
-+
-[source,options="nowrap"]
-----
-$ mvn clean install
-----
-
-[[build_and_deploy_the_quickstart]]
-==== Build and Deploy the Quickstart
-
-This section describes the basic steps to build and deploy an application. See the specific instructions in each quickstart `README` file for any variations to this process.
-
-. Make sure you start the {productName} server as described in the quickstart `README` file.
-. Open a terminal and navigate to the root directory of the quickstart you want to run.
-. Use the following command to build and deploy the archive.
-+
-[source,options="nowrap"]
-----
-$ mvn clean install wildfly:deploy
-----
-
-[[undeploy_the_quickstart]]
-==== Undeploy an Quickstart
-
-Use the following command to undeploy the quickstart.
-
-[source,options="nowrap"]
-----
-$ mvn wildfly:undeploy
-----
-
-// Getting Started with OpenShift
-include::shared-doc/openshift-getting-started-overview.adoc[leveloffset=+1]
-
-[[run_the_quickstarts_in_jboss_developer_studio_or_eclipse]]
-== Run the Quickstarts in {JBDSProductName} or Eclipse
-
-You can also start the server and deploy the quickstarts or run the Arquillian tests from Eclipse using JBoss tools. For general information about how to import a quickstart, add a {productName} server, and build and deploy a quickstart, see link:{useEclipseUrl}[Use {JBDSProductName} or Eclipse to Run the Quickstarts].
-
-ifdef::ProductRelease[]
-// Optional components are used only for the Product Releases.
-[[optional_components]]
-== Configure Optional Components
-
-The following components are needed for only a small subset of the quickstarts. Do not install or configure them unless the quickstart requires it.
-
-* xref:create_quickstart_users[Create Quickstart Users]
-* xref:configure_postgresql[Configure the PostgreSQL Database]
-* xref:configure_byteman[Configure Byteman]
-
-[[create_quickstart_users]]
-=== Create Quickstart Users
-
-Some of the quickstarts, particularly those that run in a secured mode and demonstrate security, require that you create quickstart users with different roles for authorization purposes. See https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CREATE_USERS.adoc#create_users_required_by_the_quickstarts[Create Users Required by the Quickstarts] for detailed instructions to create users required by the quickstarts.
-
-[[configure_postgresql]]
-=== Configure the PostgreSQL Database
-
-Some of the quickstarts that demonstrate transactions require that you install and configure the PostgreSQL database. See https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_POSTGRESQL_JBOSS_EAP.adoc#configure_the_postgresql_database_for_use_with_the_quickstarts[Configure the PostgreSQL Database for Use with the Quickstarts] for instructions.
-
-[[configure_byteman]]
-=== Configure Byteman
-
-A few of the quickstarts use _Byteman_ to demonstrate distributed transaction processing and crash recovery. See https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_BYTEMAN.adoc#configure_byteman_for_use_with_the_quickstarts[Configure Byteman for Use with the Quickstarts] for instructions.
-// END ifdef::ProductRelease[]
-endif::[]
-
-// The following is included for all versions: WildFly, JBoss EAP, EAP CD and EAP XP
-[[available_quickstarts]]
-== Table of Available Quickstarts
-
-All available quickstarts, which are listed in the following table, can be found here: {githubRepoUrl}.
-
-Each quickstart provides the list of technologies demonstrated by the quickstart and the required experience level needed to build and deploy it. Click on the quickstart link in the table to see more detailed information about how to run it. Some quickstarts require deployment of other quickstarts. This information is noted in the `Prerequisites` section of the quickstart `README.html` file.
-
-NOTE: Some of these quickstarts use the H2 database included with WildFly. It is a lightweight, relational example datasource that is used for examples only. It is not robust or scalable, is not supported, and should NOT be used in a production environment!
-
-//
You can follow these steps to build the application to test for compile errors or to view the contents of the archive. See the specific quickstart README
file for complete details.
This section describes the basic steps to build and deploy an application. See the specific instructions in each quickstart README
file for any variations to this process.
Use the following command to undeploy the quickstart.
A devfile is a file that describes and define a development environment:+
The source code.
+The development components, such as browser IDE tools and application runtimes.
+A list of pre-defined commands.
+Projects to clone.
+A devfiles is a YAML file that CodeReady Workspaces consumes and transforms into a cloud workspace composed of multiple containers. You can find more details in the End-user Guide for Red Hat CodeReady Workspaces.
+We provide sample Red Hat CodeReady Workspaces or Eclipse Che devfiles to build and run the kitchensink-jsp Quickstart with this cloud IDE.
+
+ Important
+ |
++The devfiles provided are UNSUPPORTED. They are provided as examples only. + | +
To create your workspace you can either copy and paste the content from our devfiles accessible at crw-java8-maven-eap.yaml and crw-java11-maven-eap.yaml.
+Another solution is to paste the URL:
+and let the IDE download the files.
+If you want to try this Quickstart on the Developer Sandbox for Red Hat OpenShift you can use the following links :
+
+ Important
+ |
++When using the Java 8 devfile, you must not install the Java11 plugin in your workspace as it will conflict with the selected Java8 plugin and this will break debugging (see CRW-1789 for more details). So don’t install the proposed plugins when you are prompted. + | +
For information about how to download and install Red Hat CodeReady Workspaces, see the Installation Guide.
+For information about how to configure JBoss EAP within Red Hat CodeReady Workspaces, see End-user Guide.
+For information about how to import the quickstarts into Red Hat CodeReady Workspaces, and for examples of how to build and deploy a basic quickstart, see Using the Quickstart Examples in the Getting Started Guide for JBoss EAP.
+See Red Hat CodeReady Workspaces on the Red Hat Developer Program website for additional information.
+You can also start the server and deploy the quickstarts or run the Arquillian tests from Eclipse using JBoss tools. For general information about how to import a quickstart, add a JBoss EAP server, and build and deploy a quickstart, see Use Red Hat CodeReady Studio or Eclipse to Run the Quickstarts.
@@ -651,7 +774,7 @@The following components are needed for only a small subset of the quickstarts. Do not install or configure them unless the quickstart requires it.
@@ -670,19 +793,19 @@Some of the quickstarts, particularly those that run in a secured mode and demonstrate security, require that you create quickstart users with different roles for authorization purposes. See Create Users Required by the Quickstarts for detailed instructions to create users required by the quickstarts.
Some of the quickstarts that demonstrate transactions require that you install and configure the PostgreSQL database. See Configure the PostgreSQL Database for Use with the Quickstarts for instructions.
A few of the quickstarts use Byteman to demonstrate distributed transaction processing and crash recovery. See Configure Byteman for Use with the Quickstarts for instructions.
All available quickstarts, which are listed in the following table, can be found here: https://github.com/jboss-developer/jboss-eap-quickstarts/.
@@ -875,6 +998,14 @@none
EJB, JTA, Clustering
Yes
The ejb-txn-remote-call
quickstart demonstrates remote transactional EJB calls over two application servers of JBoss EAP.
Intermediate
none
CDI, JSF, JPA, EJB, JTA
Yes
JSP, JPA, JSON, Spring, JUnit
Yes
The spring-kitchensink-basic
quickstart is an example of a Jakarta EE 8 application using JSP, JPA and Spring 4.x.
The spring-kitchensink-basic
quickstart is an example of a Jakarta EE 8 application using JSP, JPA and Spring 5.x.
Intermediate
none
JSP, JPA, JSON, Spring, JUnit
Yes
The spring-kitchensink-springmvctest
quickstart demonstrates how to create an MVC application using JSP, JPA and Spring 4.x.
The spring-kitchensink-springmvctest
quickstart demonstrates how to create an MVC application using JSP, JPA and Spring 5.x.
Intermediate
none
none
JPA, JAX-RS, OpenShift, Galleon
No
The todo-backend
quickstart demonstrates how to implement a backend that exposes a HTTP API with JAX-RS
Intermediate
none
Web Socket, CDI Events, JSON, SSL
Yes