Tag Archives: Java EE7

Adopt-a-JSR for Java EE


Adopt-a-JSR for Java EE

Sou Java logoChennai JUG logoLondon Java Community logoBelgium JUG logoMorocco JUG logoPeru JUG logoIndonesia JUG logoCongo JUG logoSilicon Valley JUG logoMadrid JUG logoCologne JUG logoHyderabad JUG logoCEJUG LogoFaso JUG logoJozi JUG logoAdopt-a-JSR is a grassroots initiative by JUG leaders to encourage JUG members to get involved in a JSR. The goal is to give rank-and-file Java developers a way to contribute directly to Java specifications through their local JUGs. There are many ways to contribute – from just sending in some feedback on a specific issue all the way to writing code for a reference implementation (RI) or compatibility test kit (TCK).

Adopt-a-JSR was launched towards the end of the Java EE 7 time-frame and has already been a success. Numerous developers have participated through many JUGs across the globe. We hope to significantly build upon that momentum for Java EE 8 – perhaps making it the most community driven Java EE release to-date.

2 Ways of Passing Properties / Parameters in Java EE 7 Batch


2 Ways of Passing Properties / Parameters in Java EE 7 Batch

When it comes to the Java EE 7 Batch Processing facility, there are 2 ways in passing properties / parameters to the chunks and batchlets. This quick guide shows you the 2 ways, which could be use very frequently when developing batch processing the Java EE 7 way.

JAVA EE 7 WITH ANGULAR JS – CRUD, REST, VALIDATIONS – PART 2


JAVA EE 7 WITH ANGULAR JS – CRUD, REST, VALIDATIONS – PART 2

This is the promised follow up to the Java EE 7 with Angular JS – Part 1. It took longer than I expect (to find the time to prepare the code and blog post), but it’s finally here!

Java EE7 and Maven project for newbies – part 7 – #jpa2 and Unit testing using #arquillian / #WildflyAs 8.1 #maven #jboss – using a real Datasource (#postgresql)


Java EE7 and Maven project for newbies – part 7

Resuming from the previous parts

Part #1, Part #2, Part #3, Part #4, Part #5 , Part #6

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 (called ExampleDS). But what about a real DBMS? In this post we are going to extend a bit the previous work, use the same principles and
  • test towards a running PostgreSQL in our localhost
  • use some of the really nice features of the ShrinkWrap API, Arquillian Offers.