Ask questions and see you at June, 7th, 8.PM. CEST: https://youtu.be/Uz1nLi5APVw
Also checkout recent episode:
Please keep the questions Jakarta EE-stic. Means: as short and as concise as only possible. Feel free to ask several, shorter questions. Upcoming airhacks.tv events are also going to be announced at meetup.com/airhacks
I heard you say several times that you never use an ear and you only use wars. I know there are several issues with using ear's probably because some specs do not define the behaviour when an ear is used and as such I understand why you would not use an ear.
But how would you then handle it when you need some bean that is to be used by all wars. In an ear, all wars can use it.
I can imagine if it's a jar with code and no state then you could include it in every war but if it's big then it would duplicate jars.
But if it's some bean with a central state like a cache or some client that you really only want to instantiate once, how would you handle that.
Of course you could wrap things in a rest api so wars could call each other but that would slow things down because of the extra http communication layer.