Ondro Mihályi
Ondro Mihályi
I believe it's like @arjantijms says, we should clarify the behavior in the specification and javadoc. The test is correct and ensures a valid and expected behavior. But the behavior...
I'm curious what other committers think. @m0mus , @dblevins , @keilw , @rdebusscher , and others, what's your opinion?
The TCK used wasn't the final version, putting this on hold until the final TCK is released and GlaasFish passes it.
Turned into a request for OpenMQ instead of GlassFish. The TCK used is a final one, no further modifications are planned, except possibly an update to the TCK guide that...
Updated to 39th build in Jenkins.
I've updated the info according to the build https://ci.eclipse.org/openmq/job/2_openmq-run-tck-against-staged-build/40/ as @pzygielo requested.
The bottom line is that we could create a new lite messaging profile that would support AMQP or STOMP. In other words, it would be easy enough to implement such...
The javadoc for [JMSContext.setAutoStart()](https://github.com/jakartaee/messaging/blob/e1787dbe2ca3aaa00ccf55d7b7b50f9279fb63e9/api/src/main/java/jakarta/jms/JMSContext.java#L340) already states that the default behavior is that underlying connection will be started automatically when a consumer is created. So we just need to write something...
Hi @vongosling, I'm reacting to your comment here and to your email in https://www.eclipse.org/lists/jms-dev/msg00151.html as well. First about your concerns about container environment. I believe you don't need to be...
It's not relevant, the latest Javadoc is OK.