Ask questions and see you at October, 5th, 8.PM. CET: https://vimeo.com/event/154379
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
Hello Adam, it's the first time I write in your Gist I hope to be as concise as possible and thank you very much for your tutorials and courses, you are a guru to me.
Question 1: Often/always in our projects happen to have configurations (url for database connections, properties of connections to queues, simple application FLAGs, etc. ) in a table of "configuration" within databases, configurations that are typically encapsulated within Bean Singleton and loaded when the application starts with a call to database and column mapping -> class attributes. Often the need arises also to do a hot refresh of such configurations in case one of those flags changes, so the idea was to expose a dedicated service only for the refresh of the Singleton bean. Do you consider that a good approach? Would you have a valid security option to encapsulate this information without having to resort to databases?
Question 2: Considering that the scenario at question 1 , is mainly due to the deploy environment with Tomcat, migrating such applications to WildFly I was thinking of using the Microprofile specifications in full, specifically MicroprofileConfig for injecting values ( url db , url queue, application flags etc...) directly from properties files. But I think the customer won't be happy about it, considering that some of that data is still within the source code. Do you have any idea how to use this specification in cases like the one mentioned above?
Thank you again, great job