Win a copy of Testing JavaScript Applications this week in the HTML Pages with CSS and JavaScript forum!

Rhuan Rocha

Author
+ Follow
since Aug 25, 2018
Cows and Likes
Cows
Total received
5
In last 30 days
0
Total given
0
Likes
Total received
2
Received in last 30 days
0
Total given
1
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Rhuan Rocha

Thank you guys!

I 'm happy for this forum. If you want to know about news of Jakarta EE and my new jobs about Jakarta EE, follow me on my site. My site.

If you want propose a new topic to my posts, send me on my site.

Thank you for all!
Rhuan Rocha
Hello paul nisset,

Thank you for question!

Perfect!

The diference is how these patterns are implemented and what are the real challenge of Java EE 8. The Design Patterns (GoF Patterns) are focused on the relationship between classes and objects, but the patterns used on Java EE are focused on the relationship between components (enterprise patterns), and USES tsome GoF Patterns. The diference is how it is implemented.

One specific feature that help us to create a decoupled application using Java EE 8 is Event in CDI, that permit us use the reactive programming with Java EE 8.

Regards,
Rhuan Rocha  
Hello paul nisset,

Thank you for question!

What would be two or three things that programmers should be doing differently with JEE 8 and why?

1) The Java EE is an umbrella project that have a set of specs. We need understand the use of these specs and decouple the application from vendors.

2) We need understand the relationship between components on Java EE. Enterprise patterns are pattern to solve problems about relationship between component and we shouldl use these patterns will turn the application better.

3) Write a decoupled codes. If we will use lambda or any tools of Java is less important (is less important but is important to any application in Java). The most important is write a decoupled code.

Regards,
Rhuan Rocha
Hello Divya Shiv,

Thank you for question!

In this book we focus on the enterprise patterns and the implementation using the best practices of Java EE 8. However, the chapter 1, 2 and 3 provide an insight into the inside of some Java EE tools. Furthermore, we covered a new view of a some patterns that works in a high level. These patterns we called operational patterns.

Regards,
Rhuan Rocha  
Hello Dhwani Parekh,

Thank you for question!

Thank you Meenakshi Sundar for answer!

I and João are passionate for Java and Java EE/ Jakarta EE and we want to share our experience with people. I think this book will help Java EE/Jakarta EE developer to create better applications using best practices.

Regards,

Rhuan Rocha
Hello Esteban Suarez,

Thank you for question again. I'm happy for help you.

To reactive programming using Java EE 8 you can see the Event in CDI and to AOP you can see CDI Interceptor and EJB Interceptor. In my book you will see topics about that and can increase your knowledge about these techniques.


Regards,
Rhuan Rocha
Hello Meebakshi Sudar,

Thank you for question.

It is a very good question. The jakarta EE is based on Java EE 8 and after the new features will be added into Jakarta EE. In this step, the mission is migrate the Java EE 8 to Jakarta EE. The Java EE 8 is JDK8 based, then the Jakarta EE will be JDK8 based.

Regards,
Rhuan Rocha
Hello Meenakshi Sundar,

Thank you for question!

I guess it's early to talk about that. The Jakarta EE is migrating now and the first version of Jakarta EE will be the same specs, TKs and RIs them Java EE 8. However, the Spring Framework works as a high level abstraction that permit us write application with less code lines. With this the Spring Frameworks needs define a major set of configurations. The Spring Framework is more configurable and Jakarta EE is more programatic. With this, Jakarta EE tend to suffer less with this problem.

Regards,
Rhuan Rocha
Hello Esteban Suarez,

Thank you for question!

1) We covered an overview about design patterns on the first chapter. Throughout of book we explained about enterprise patterns, reactive patterns and the best practices of uses of current techniques in Java EE 8, like reactive programming and aspect-oriented programming. The implementation os some enterprise patterns uses some design patterns and we covered that. I think the topic about reactive patterns and aspect-oriented programming are very important to understand now, because I guess with this migration from Java EE to Jakarta EE we will have many evolution about these techniques in the future.

2) In this book we explained about deployment patterns and performance and monitoring on the topic of operational patterns. This topic is interesting because we covered a new view about some kind of patterns that acts on high level.

I will post some contents about that on my site as a overview. Access my site and follow me.

Site: Jakarta EE with Coffee

Regards,
Rhuan Rocha
Hello everyone!

If you want to know about news of Jakarta EE, follow me in my site Jakarta with Coffee and look.

Jakarta with Coffee

Thank you,
Rhuan Rocha
Hello, Krzysztof Rams!

No, we don't covered references or example related to Spring Framework directly. But, I explained about some patterns used into Spring, like Application Controller Pattern and Front Controller Pattern. These concepts will help you to understand how Spring Framework works.

Thank you,

Rhuan Rocha
Hello, Thank you for question.

This book don't covered new design patterns, but covered the design patterns with another view. In the Java EE world we work with components and the problems are about the relationship between components. Thus, we have the enterprise patterns, that provide solutions to problems about the relationship between component. Some of these enterprise patterns are implemented using design patterns (GoF). In this book we covered the diference between design patterns and enterprise patterns and how to implement them using Java EE 8.

Regards,

Rhuan Rocha