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,
Hi Adam, do you plan to add Eclipse Glassfish to docklands? Their first release will be out soon. Please see AdamBien/docklands#28 . Thank you!
Hi Adam, some of my microservices depend on apache poi which leads to a war >18MB. How in general do you build an application server (docker) including static dependencies (which could also easily be updated)? Thank you from Landshut :)
Hi Adam
Hi Adam. I was reading your post about ManagedScheduledExecutorService replacing EJB Timer. Do you have an idea how to mock this resource using Weld (I've read something about binding a resource building the WeldInitiator but it seems weird...)
Hi Adam,
as consistency of data across microservices is not handled by the relational databases any more,
are you favour of manually handling the consistency (by adopting two-phase commit, retries logic etc) or adopting
a tool that provides eventual consistency, such as an event sourcing tool, for example debezium?
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!
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, Are you using any kind of CMS for your blog stuff, or are you write HTML pages manually?
Thank you.