Series it's been a long time since my last post, for this series of tutorials. it's time to resume and add new features on our simple project. As I have mentioned in previous posts, this series of posts is targeting mostly Maven and JavaEE7 newcomers, I welcome any questions or comments (and fixes) on the contents …

Series Previous Post, Next Post In the previous post (num 6) we discovered how we can unit test our JPA2 domain model, using Arquillian and Wildfly 8.1 In the previous post we made a simple configuration decision, we used the internal H2 database that is bundled with Wildfly 8.1 and the already configured Datasource …

Series Previous Post, Next Post In the previous post (part 5), we discovered how we can unit test using Arquillian, our EJB services, deploying them in a real instance of Wildfly8.1 application server. Extending the previous example we will add some more configuration and code, so that we can add unit tests that …

Series Previous Post, Next Post This is the first extra post, based on the maven JavaEE7 demo project I am building on this series of blog posts. We have already defined a solid structure and some modules. One very common case in an application like this, is to use Arquillian (+ JUnit), a god sent framework, that …

We are resuming for the 4th part, our simple project currently has a web maven module (a war) an ejb module (ejb) holding our stateless session beans (EJB 3.1) and a second (ejb) module holding our entity beans (JPA2) but we are still missing the one to package them all, archive, which will be of ear_ type (aka …

Series Previous Post, Next Post We are resuming for the third part, we already have a parent pom and we have already defined the pom for our war module. In our original setup we have defined that our application is going to include a services jar, in the form of an ejb jar. This where our Enterprise Java Beans are …

Series Previous Post, Next Post We have just defined, our parent pom. A special type of pom that eventually defines the libraries that our application is going to use. It also configures all the maven tools used in order to package each module of our application. You can check out the part -1 sample code here. So up …

Series Next post Why ? Many times, I am trying to resolve several basic or complex Maven / Java EE project structure issues, on my day work. In order to provide the solutions, I often end up experimenting with the project structure, test my deployment on different application servers and fine grain my configuration. …