You can deploy many of the quickstarts and run the Arquillian tests from Eclipse using JBoss tools. However, the EJB Client currently has limited support in the Eclipse Web Tools Platform (WTP). For that reason, some quickstarts that ship with Red Hat JBoss Enterprise Application Platform are not supported in Red Hat CodeReady Studio.

This guide includes the following information.

For information about how to download and install Red Hat CodeReady Studio, see the Installation Guide .

For information about how to configure JBoss EAP within Red Hat CodeReady Studio, see Getting Started with CodeReady Studio Tools .

For information about how to configure Maven and Red Hat CodeReady Studio for use with the quickstarts, see Configure Maven for Use with Red Hat CodeReady Studio in the Development Guide for JBoss EAP.

For information about how to import the quickstarts into Red Hat CodeReady Studio, 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.

For instructions to run the Arquillian tests using the Maven command line, see Run the Arquillian Tests .

Your quickstart project folder must be located outside of your IDE workspace. If your quickstart project folder is located within the IDE workspace when you import it into Red Hat CodeReady Studio, the IDE generates an invalid project name and an invalid WAR archive name. Be sure your quickstart project folder is located outside the IDE workspace before you begin!

Be sure to follow the instructions in the quickstart README.adoc file to add any required application users or make the appropriate server configuration changes.

More complex quickstarts may require special instructions to run properly in Red Hat CodeReady Studio. This document describes some of these special situations.

If you see errors or warnings when you import or run a quickstart, see the list of Known Issues for JBoss EAP Quickstarts below for an explanation.

This starts the server, deploys the application, and opens a browser window that accesses the running application.

To undeploy the project, right-click on the project and choose Run As → Maven build . Enter wildfly:undeploy for the Goals and click Run .

This starts the server, deploys the application, and opens a browser window that accesses the running application.

To undeploy the project, right-click on the EAR subproject and choose Run As → Maven build . Enter wildfly:undeploy for the Goals and click Run .

Right-click on the Java client project and choose Run As → Java Application . In the Select Java Application window, choose the client class and click OK .

The client output displays in the Console window.

To undeploy the project, right-click on the server subproject and choose Run As → Maven build . Enter wildfly:undeploy for the Goals and click Run .

Drag and Drop mode: Click to multi-select the projects, then drag and drop them on the running JBoss EAP server. This deploys the projects to the server without opening the browser.

Batch mode: In the Servers tab, right-click on the server and choose Add and Remove . If the quickstart projects are the only projects in the list, click Add All . Otherwise, use multi-select to select them and click Add . Then click Finish .

Right-click on the individual projects and choose Run As → Run on Server . A browser window appears that accesses the running application.

To undeploy the projects, right-click on the subprojects in the reverse order of how they were deployed, and choose Run As → Maven build . Enter wildfly:undeploy for the Goals and click Run .

Right-click on the quickstart project in the Project Explorer tab and choose Run As → Maven build .

Enter clean verify -Parq-remote in the Goals input field and click Run .

Eclipse Web Tools Platform (WTP) can not deploy simple JARs to the JBoss EAP server. For this reason, quickstart subprojects that would normally deploy shared artifacts as JARs deploy them instead as EJB JARs. You can ignore this warning.

If the quickstart project uses JPA to access a database, you will see the following warning when you import the project into Eclipse. You can ignore this warning as it only applies to the local connection in the Eclipse development environment and does not affect the JBoss EAP runtime deployment. To eliminate this warning, you must configure the database connection in the Eclipse project settings.

This error can occur with quickstart projects that are composed of multiple subprojects. This is a known issue. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=459810 .

This warning is intermittent and can occur with any quickstart project that uses Hibernate. This is a known issue. For more information, see https://issues.jboss.org/browse/JBIDE-17483 .

The JBoss EAP 6 quickstarts demonstrate Java EE 6 features and are built on Java SE 6. Red Hat CodeReady Studio requires Java 8 to run, but is still capable of launching runtimes with various versions of Java. You can ignore this warning, or you can install a JDK 6 on your machine and add it to the Eclipse Java Runtime Environment by choosing Preferences → Java → Installed JREs .

Quickstarts that require Knowledge Base capabilities to be enabled on the project display this warning. To resolve it, right-click on the warning message in the in the Red Hat CodeReady Studio Problems window and choose Quick Fix . This opens a window with the fix Enable Knowledge Base capabilities on project <project-name> selected. Make sure all projects are selected and click Finish to resolve the warning.

This error can occur with quickstart projects that are composed of multiple subprojects. The import of a project on one thread may trigger Eclipse to refresh a project on another thread making the project state appear to be inconsistent. To resolve the errors, right-click on the parent project in Red Hat CodeReady Studio and choose Maven → Update Project . Make sure all the projects are selected and click OK . This should resolve the errors.

This error occurs if endorsed directories are defined in the maven-compiler-plugin configuration of the quickstart POM file. To resolve the error, right-click on error in the Red Hat CodeReady Studio Problems window and choose Quick Fix . This opens a window with the fix Run 'mvn process-sources' to execute dependency:copy selected. Click Finish to resolve the error. For more information, see JBoss Maven Integration .

You can ignore this m2e warning. It can occur in child projects where the dependency versions are defined in the parent POM file. For more information, see Bug 346725 - "Overriding managed version" in pom.xml should not be a warning severity .

You can ignore this error. This is a known Eclipse issue. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=415786 . To turn off WSDL validation in Red Hat CodeReady Studio, choose Windows → Preferences , select Validation , find WSDL Validator in the list, and uncheck the Manual and Build selections.

You can ignore this error. This is a known Eclipse issue. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=415786 . To turn off WSDL validation in Red Hat CodeReady Studio, choose Windows → Preferences , select Validation , find WSDL Validator in the list, and uncheck the Manual and Build selections.

This warning occurs when you import a quickstart that contains a WSDL file into Red Hat CodeReady Studio. You can ignore this warning. It is a known Eclipse issue. For more information, see https://bugs.eclipse.org/bugs/show_bug.cgi?id=535813 .

You can ignore this error. This is a known issue with the jboss-ejb3-spec-2_0.xsd schema file. See https://bugzilla.redhat.com/show_bug.cgi?id=1193543 .

You can ignore this error. This is a known issue with the jboss-ejb3-spec-2_0.xsd schema file. See https://bugzilla.redhat.com/show_bug.cgi?id=1193543 .

You can ignore this error. This is a known issue with the jboss-ejb-iiop_1_0.xsd schema file. See https://bugzilla.redhat.com/show_bug.cgi?id=901186 and https://bugzilla.redhat.com/show_bug.cgi?id=1192591 .

You can ignore this error. This is a known issue with the ` jboss-ejb-iiop_1_0.xsd` schema file. See https://bugzilla.redhat.com/show_bug.cgi?id=901186 and https://bugzilla.redhat.com/show_bug.cgi?id=1192591 .

You can ignore this error. This is a known issue with the jboss-ejb-container-interceptors_1_0.xsd schema file. See https://issues.jboss.org/browse/WFLY-4365 .