Ask questions and see you at November, 5th, 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 November, 5th, 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, Could you give your opinion? If I want to migrate a JSF application in the future, should I use an existing frameworks, like vue.js?, or Do I use web components?, Which one could be more cost-benefit better in a long term period?
What do you think about RxJava, Is this similar to the non blocking architecture of node.js? Is this better than use @asynchronous annotations? Is this compatible with a JEE application at specification level (compliance)?
Regarding Apache POI in JavaEE. In https://www.youtube.com/watch?v=DzaDhAx12gc&feature=youtu.be&t=2292 you say that you make a docker base image, put POI there and all microservices rely on this base image.
Do you mean by that, that you put POI jar's in for example WildFly in a jboss module (\modules\system\layers\base\org\apache\poi), reference this module in jboss-deployment-structre.xml
and in pom.xml
use POI as <scope>provided</scope>
?
Hi Adam, i would like to know you opinion about the IBM-RedHat merging in regards to Java EE ecosystem, i mean we have now Jakarta EE and the specs of "new" framework are not set It is even more interesting , because some of my clients expressed a concern about further support of legacy Java EE based projects, i know that first version of Jakarta EE would be backwards compatible with Java EE8 , but what will happen after that? I saw the discussion on google mailing list and majority of people wish to drop some old technology (EJB, JMS) in favor of new solutions, so what is your take on this problem? My current best advise to the clients basically will be just to get active and raise some concerns in Jakarta EE Specification Process in eclipse community.
Hi Adam,
If an exception/error occurs in a JAX-RS method on the server, the stack trace is returned to the client. The client shouldn't see these details. How to prevent it?
I am using an H2 in-memory database during development for my JPA entities (Wildfly default I think). How can I view the tables during runtime? Anything that integrates with Eclipse?
Hi Adam,
I have a short question for the BCE-structuring with multiple implementations of a given "domain-aspect". Given the case, there is a payment-feature in an application. And the payment can be performed via different payment-providers.
So, basically, I would have:
/business/payment/ [b/c/e] but inside, I will have PaymentProviderA, PaymentProviderB and so on. All payment-provider should behave the same, so there is an "AbstractPaymentController", so that the concrete PaymentControllers only need to implement there specific API-implementation of the specific PaymentProvider.
Would it be correct to structure the packages as following, or do you have a better idea:
.../business/payment/boundary/PaymentResource.class
.../business/payment/control/AbstractPaymentController.class
.../business/payment/PaymentProviderA/control/PPAController.class
.../business/payment/PaymentProviderB/control/PPBController.class
Thank you very much in advance from Hamburg
Ulrich
Hi Adam
I'm working on a project where we have too many relationship with a main jpa entity. Let's say entity A, which has @OneToMany and @manytoone relationship whith 10 other different entities. But this way the project is tiglhy coupled.
We are trying to find a way to separate code. Maybe by splittin the server side app in microservices. Or simpler by splitting server side code in different jars packaged all of them to one ear or war(i checked your plugin implementation in jee )
If we want to pass a feature in another microservice or jar and want to gve the posibbility of producing different packages of our app with more or less features included , and if there is an entity which is tiglhy coupled with @OneToMany with the A @entity this could not happen.
How to handle with this problem?
Vaggelis