Zoltan Raffai

Thanks Arthur!

You've got true. I will augment it with a note according to this.

Oh, well in this case. The str and s should be the same String.

The problem with this approach that it has a big performance overhead.

I cheked it on an eight char pattern with 1000 cycles the runtime result are:

1 vs 60 ms

With more cycles, the difference is decreasing, but still significant.

With 10000000 cycle:

748 vs 2328 ms

Hi! Now It is available on my blog: https://www.zoltanraffai.com/blog/streams-in-java-8-2/

Hopefully, it will go out to Dzone shortly as well. :)

HI Beto!

Thanks for you feedback, but I missed it. Where is the link to the collections?

Thank you!

What would you like to decide with this?

Hi! Thanks for your kindness. :)

I wrote about this in the first chapter under The Spring Boot Approach. In your configuration file, under the server section you can set the tomcat server properties. Port number, context path name etc. to run your Spring boot application with. This won't take effect under externalized tomcat. These are just for the embeeded one.

It would be best if it would work. :) Here the link from the official documentation: https://docs.spring.io/spring-boot/docs/current/reference/html/boot-features-external-config.html

The yaml variants are only working where it is written. I tried out.

Hi Brian!
It only works for .properties file. You can't handle yaml/yml files with it. So you can not solve every situation that approach.

What do you exactly mean under this article?

Thanks! I didn't know that there is such a bug in this library.

Thank you Lakhmir!

I corrected it.

Hi! For controller level error handling you should use the @ControllerAdvice annotation. Its specified exactly for Controllers where you can define different ResponseBodies with different http statuses related to the throwed exceptions.

Hi Jose!

Thanks for your perception! You've got the point. I'll examine the possibility to upgrade my article regarding this.

Actually, they all start with "final" :)

Hi! I checked your code. You're right. It works with Java-based configuration in this scenario and with Annotation as well.

I had a convention that it not work. Maybe they upgraded it in some prev versions, but I didn't find any source for that.

Thank you to reveal my mistake!

I'll update my post according to this. (Omit these lines.)

Best Regards,
Zoltan Raffai

Hi Angel!

Thanks for your thought. It's a very interesting topic!

Here you wire up the BeanFactory through Annotation, but it does not show up, what type of BeanFactory you'll get and how the RestTemplate class is configured to be achievable.

The interesting thing here, that if you configure your Spring framework to use Annotation-based bean configuration and you use the @Component annotation on your POJO-s. You will can't reach them through the native BeanFactory implementations.

As I know it's possible to achieve that: you need to write your own BeanPostProcessor where you go through the annotations.

In contrast, the ApplicationContext can auto-configure the BeanPostProcessor for itself, when the configuration is set to annotation-based.

If you use the @Autowired annotation for Dependency Injection get the beans through the ApplicationContext.

So all in all, you've got true if we not too strict because it can support.

Please let me know if missed something.

Hi!

Thank you for the feedback Frédéric!

You've got right! I'll correct it.

Best Regards,
Zoltán Raffai