How To Tackle JavaEE - DevCrowd Keynote
How to structure a JavaEE application? How to organize your code? What are the essential ingredients of a maintainable JavaEE application? How to be productive with JavaEE?
I discussed such questions during the DevCrowd keynote: http://2014.devcrowd.pl/agenda/.
Warning: I used slides in the first part of the keynote :-).
Any questions left? Prepare your questions and I will attempt to answer them …live. Drop a comment / question && see you at each first Monday of the month at 6 p.m (CET) [http://www.ustream.tv/channel/adambien]!
See you at Java EE Workshops at MUC Airport, particularly at the Java EE Architectures workshop, screencasts at: http://tv.adam-bien.com or subscribe to http://www.youtube.com/user/bienadam.!
Hi, Adam
Could you compare Java EE with OSGi, as platforms for creating maintainable applications, having in mind OSGi Enterprise specification from one side, and usage of OSGi within many of Java EE containers, like Websphere and Jboss AS.
Do we have really important differences between this platforms?
Posted by Serge on April 14, 2014 at 06:50 PM CEST #
Hi Adam,
Really nice presentation! I do not personally agree with everything but it does make a lot of sense.
One suggestion though, instead of showing mockito with @InjectMock, why you do not use the Arquillian framework and create first class citizen integration test that supports all the Java EE features?
You could also then show how to create a mock using CDI standard.
Again, keep up the good work,
Mathieu
Posted by Mathieu on April 15, 2014 at 02:40 PM CEST #
Hi Adam,
good keynote, thx. I read your book and this is good compilation behind the idea of ECB design.
I have one question though.. You told that war file is enough. I'm using maven modules for better reusing. When I'm using only war file I end up with copying code from one project to other one and I don't see any point to do this -> error prone and super slow..
So here is the question: You start always developing from scratch or you have some kind of abstract components? -> overengineering
@Mathieu
I think one reason was to much overhead. There was no point to introduce arquillian for such simple test.
Cheers,
Petr
Posted by MiX-CZ on April 28, 2014 at 03:57 PM CEST #