Hi Ken ActiveMQ Classic is "runtime" agnostic, each runtime can have a different semantic (it happened in the past in ActiveMQ Karaf).
Generally speaking, I don't consider it a requirement, so it makes sense to skip it (and we can trust our users :)). Regards JB On Sat, Dec 7, 2024 at 11:05 PM Ken Liao <kenlia...@gmail.com> wrote: > > Hi dev community, > > According to > https://jakarta.ee/specifications/messaging/3.1/jakarta-messaging-spec-3.1#restrictions-on-usage-in-jakarta-ee > Asynchronous send is not permitted in a Jakarta EE web container or > Enterprise Beans container. However, This is recommended but not required. > I have spent some time trying to find precedent for disabling a feature in > those environments in the codebase but couldn't. > > Is there any precedent for turning off a particular feature in a Jakarta EE > web container or Enterprise Beans container in ActiveMQ Classic? If not, > can we skip that requirement for implementing Jakarta 3.1 async send? > > Thanks, > Ken --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@activemq.apache.org For additional commands, e-mail: dev-h...@activemq.apache.org For further information, visit: https://activemq.apache.org/contact
