con Jboss Tools, possiamo creare un progetto composto da diversi progetti, in maven. in questo tutorial, creeremo un progetto che è basato su maven e una volta deployato sul server, sarà un file .EAR. Gli Ear, sono degli archivi ha contengono al loro interno diversi JAR (librerie e/o EJB), dei WAR (archivi per la parte di front end). Maven, permette di gestire questi progetti separatamente, e poi di collegarli tra loro. Vediamo come funzionano le cose con eclipse.
come al solito. FILE -> OTHER...
si sceglie JBOSS CENTRAL e poi Java EE EAR Project.
compare una schermata come la seguente, dove eclipse ci informa che il progetto che stiamo per creare è basato su maven.
inseriamo il nome del progetto e il package. in questo caso, ho deciso di usare il nome standard che eclipse mette come default. Analizziamo il progetto creato. in questo caso, avremo tre cartelline, nel progetto princiale nel mio caso esempioJbossProject, uno per l’ear, uno per gli ejb e uno per il war. I progetti dove realmente metteremo le classi hanno lo stesso nome delle cartelline appena create da JBOOS TOOLS, ma ovviamente saranno dei progetti MAVEN, quindi con la tipica struttura che hanno quel tipo di progetti.
Automaticamente, eclipse aprirà questo file, un file di readme, che ci permette di capire come è fatto questo progetto. e che vi ho postato qui sotto.
What is it?
———–This is your project! It is a sample, deployable Maven 3 project to help you get your foot in the door developing with Java EE 7 on JBoss WildFly.
This project is setup to allow you to create a compliant Java EE 7 application using JSF 2.2, CDI 1.1, EJB 3.2, JPA 2.1 and Bean Validation 1.1. It includes a persistence unit and some sample persistence and transaction code to introduce you to database access in enterprise Java.
System requirements
——————-All you need to build this project is Java 7.0 (Java SDK 1.7) or better, Maven 3.1 or better.
The application this project produces is designed to be run on JBoss WildFly.
Configure Maven
—————If you have not yet done so, you must [Configure Maven](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/CONFIGURE_MAVEN.md) before testing the quickstarts.
Start JBoss WildFly with the Web Profile
————————-1. Open a command line and navigate to the root of the JBoss server directory.
2. The following shows the command line to start the server with the web profile:For Linux: JBOSS_HOME/bin/standalone.sh
For Windows: JBOSS_HOME\bin\standalone.batBuild and Deploy the Quickstart
————————-_NOTE: The following build command assumes you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Build and Deploy the Quickstarts](https://github.com/jboss-developer/jboss-eap-quickstarts#build-and-deploy-the-quickstarts) for complete instructions and additional options._
1. Make sure you have started the JBoss Server as described above.
2. Open a command line and navigate to the root directory of this quickstart.
3. Type this command to build and deploy the archive:mvn clean package wildfly:deploy
4. This will deploy `target/esempioJbossProject.ear` to the running instance of the server.
Access the application
———————The application will be running at the following URL: <http://localhost:8080/esempioJbossProject-web>.
1. Enter a name, email address, and Phone nubmer in the input field and click the _Register_ button.
2. If the data entered is valid, the new member will be registered and added to the _Members_ display list.
3. If the data is not valid, you must fix the validation errors and try again.
4. When the registration is successful, you will see a log message in the server console:Registering _the_name_you_entered_
Undeploy the Archive
——————–1. Make sure you have started the JBoss Server as described above.
2. Open a command line and navigate to the root directory of this quickstart.
3. When you are finished testing, type this command to undeploy the archive:mvn wildfly:undeploy
Run the Arquillian Tests
————————-This quickstart provides Arquillian tests. By default, these tests are configured to be skipped as Arquillian tests require the use of a container.
_NOTE: The following commands assume you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See [Run the Arquillian Tests](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/RUN_ARQUILLIAN_TESTS.md) for complete instructions and additional options._
1. Make sure you have started the JBoss Server as described above.
2. Open a command line and navigate to the root directory of this quickstart.
3. Type the following command to run the test goal with the following profile activated:mvn clean test -Parq-wildfly-remote
Investigate the Console Output
———————
You should see the following console output when you run the tests:Results :
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0Investigate the Server Console Output
———————
You should see messages similar to the following:INFO [org.jboss.as.server] (management-handler-thread – 9) JBAS018559: Deployed “test.war”
INFO [org.jboss.tools.example.controller.MemberRegistration] (http–127.0.0.1-8080-2) Registering Jane Doe
INFO [org.jboss.tools.example.test.MemberRegistrationTest] (http–127.0.0.1-8080-2) Jane Doe was persisted with id 1
INFO [org.jboss.weld.deployer] (MSC service thread 1-6) JBAS016009: Stopping weld service for deployment test.war
INFO [org.jboss.as.jpa] (MSC service thread 1-1) JBAS011403: Stopping Persistence Unit Service ‘test.war#primary’
INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-1) HHH000227: Running hbm2ddl schema export
INFO [org.hibernate.tool.hbm2ddl.SchemaExport] (MSC service thread 1-1) HHH000230: Schema export complete
INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) JBAS010409: Unbound data source [jboss/datasources/esempioJbossProjectTestDS]
INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015877: Stopped deployment test.war in 19ms
INFO [org.jboss.as.server] (management-handler-thread – 10) JBAS018558: Undeployed “test.war”Run the Quickstart in JBoss Developer Studio or Eclipse
————————————-
You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see [Use JBoss Developer Studio or Eclipse to Run the Quickstarts](https://github.com/jboss-developer/jboss-developer-shared-resources/blob/master/guides/USE_JBDS.md)Debug the Application
———————If you want to debug the source code or look at the Javadocs of any library in the project, run either of the following commands to pull them into your local repository. The IDE should then detect them.
mvn dependency:sources
mvn dependency:resolve -Dclassifier=javadoc
ultimatecodingblog 