Ondro Mihályi

Duplicate of #328

Hi @t1 , Did you review the proposal in https://github.com/tomitribe/jms-proposals/blob/master/messaging-client/src/test/java/org/example/BuildAndNotify.java? Do you think it's viable and close to what you expect and described on the mailing list? There's an interface...

OK. This sounds close to what is proposed in the tomitribe/jms-proposals repository, and specifies some default behavior so that annotations are applied only if needed. To get things moving, I've...

This isn't relevant anymore, it was done by https://github.com/jakartaee/messaging/commit/27a1ba61e02220f403e73da87156cea00be2b9b7

This is a very old issue and it's now superceeded by https://github.com/jakartaee/messaging/issues/243. I'm closing this issue.

I agree with @hantsy, no interface is needed. And I also like that any CDI bean can be turned into a JMS observer. However, I'm not sure whether a single...

> I think the TransactionManager is intended for access by the application server (rather than user components) This is true. But application server components (like EclipseLink or Hibernate) may be...

I never understood why it's required that those classes implement a no-arg constructor. If there's a reliable technical solution how to relax this, I'm strongly in favor. It would allow...

I'm definitely for providing a default producer for injecting ManagedExecutorService, ContextService and anything else that can be injected using @Resource now (e.g. ManagedScheduledExecutorService, ManagedThreadFactory), as in the original proposal by...

We should also remember that some applications may already contain producers for the default concurrency services, such as: ``` @ApplicationScoped public class ExecutorProducer { @Resource @Produces ManagedExecutorService executor; } ```...