Effective Java EE Workshop Available For Streaming And Drm-Free Download

4 hours of Effective Java EE Workshop "On Demand" or 42+ videos are available for streaming and drm-free download.

During the workshop I'm building a "ToDo / Reminders" app with focus on productivity, design and pragmatism covering: Maven, BCE structure, testing (unit, integration and system-tests), JAX-RS, Bean Validation, JSF, JPA, WebSockets, exception handling, monitoring, CDI and EJB.

Any questions left? Then see you at each first Monday of the month at 6 P.M. live.

Also see you in person at Java EE Workshops at Munich Airport, Terminal 2 or Virtual Dedicated Workshops / consulting


Got hold of this the second I heard about it and I can report it is excellent. Learning a lot and great to now always have these available anytime to refer to whenever I need your insights on a particular Java EE related topic!

Posted by Geertjan on August 18, 2015 at 08:47 AM CEST #

can you download the sources which are discussed in the videos?

Posted by TJ on August 18, 2015 at 09:51 AM CEST #

Hi Adam,

I started watching your workshop and i don't understand why did you create another project for the jax-rs testing and didn't use the test directory in the your main project.
Can you please explain?


Posted by Eyal on August 18, 2015 at 09:04 PM CEST #

If I already have experience with Java EE (one completed project) and several years of Java experience (mostly Spring), should I go straight to Effective Java EE 7 or do you recommend first taking the Bootstrap?

Posted by Venomous Programmer on August 19, 2015 at 08:22 AM CEST #


you will find the sources here: https://github.com/AdamBien/doit



Posted by on August 20, 2015 at 01:05 PM CEST #


The Java EE Bootstrap course covers the maximal amount of Java EE for the realization of minimal amount of business logic.

The Essential Java EE 7 explains how to implement a simple app with the least amount of technology in pragmatic way.

If you are more interested in real world and less in Java EE mechanics, go straight to the Essential workshop,



Posted by on August 20, 2015 at 01:08 PM CEST #

Hi Adam

Thanks for the Effective Java EE course. It was very informative. I download the source code from Github and try to run in my Netbeans 8 IDE but encountered the following issue:

With Wildfly 8.1 or 9 - I get the following error when I try to run the application (I tried both inside Netbeans IDE and also separately deploying the war in Wildfly management console)
Caused by: org.jboss.weld.exceptions.IllegalArgumentException: WELD-001456: Argument resolvedBean must not be null
With GlassFish 4.1 - The application deployed fine. However, if I try to save some values for "ToDo" I get the following error

at com.airhacks.doit.business.reminders.boundary.ToDoManager$Proxy$_$$_Weld$EnterpriseProxy$.save(Unknown Source)
at com.airhacks.doit.presentation.Index.save(Index.java:55)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

Any inputs to resolve the issue is appreciated.

Thanks in Advance !

Posted by Paddy on August 26, 2015 at 08:21 PM CEST #

I just got a workaround for the deployment issue. (Caused by: org.jboss.weld.exceptions.IllegalArgumentException: WELD-001456: Argument resolvedBean must not be null) . Looks like there is an issue with CDI Injection in Entity Listener in Wildfly (https://issues.jboss.org/browse/WFLY-2387). Surprisingly, removing the CDI injection resolved the deployment issue (in Wildfly 9) as well as the runtime issue (in Glassfish 4.1)

For now, I just removed the CDI Injection in ToDoAuditor.java to resolve the issue.


Posted by Paddy on August 30, 2015 at 07:21 AM CEST #

Hello Adam,
EffectiveJavaEE is amazing, Congratulations.

I have a question, I was running the test cases and I realize that Valid annotation in the save method some time does not work, because when you send a malformed object this throw a error 400, this is fine, I modify the object in order to have a 201 response, and it is fine too, but when I back to the first test, the endpoint throw a 500 error. If I run again this test the test work again and throw a 400 error again, why this happend?

Posted by Petter on February 06, 2017 at 08:04 PM CET #

Post a Comment:
  • HTML Syntax: NOT allowed
...the last 150 posts
...the last 10 comments