Ask questions and see you at December, 3rd, 6.PM. CET: http://www.ustream.tv/channel/adambien
Also checkout recent episode:
Please keep the questions Java EE-stic. Means: as short and as concise as only possible.
Ask questions and see you at December, 3rd, 6.PM. CET: http://www.ustream.tv/channel/adambien
Also checkout recent episode:
Please keep the questions Java EE-stic. Means: as short and as concise as only possible.
Hi Adam,
As i can understand @Inject does not use pooling vs @ejb which uses pooling. This means that it is slower if we use @Inject due to object creation?
Hello, as Adam says it depends on Application Server, as i know for instance WildFly does not use pools.
Regarding behaviour on GlassFish / Payara Application Servers:
If you are injecting component via @Inject and this is Stateless component - it will use object pools.
If you are injecting POJO with @Inject - it depends on scope of injected component.
So my recommendation is - use @Inject everywhere.
Thanks.
Hi Adam,
Have you made any example attempts to configure your Docklands projects with microprofile-friendly writing of all outputs to stdout? There seems to be a diverse set of behaviors across application servers for what to put to initial stdout, when to cut over to a log file, where to write error messages, and what general log files to produce; let alone roll over frequency, etc etc etc. It would be nice, and best practice, to just dump all logging to stdout while in a container.
Bonus question if you have time: do logging frameworks have any future given increased containerization efforts?
Thanks!