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,
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 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.