* feat(tck): adding Jakarta Messaging 3.1 TCK (#1713) * feat(client): update JMS version metadata to Jakarta Messaging 3.1 (#1718) ActiveMQ reports JMS version as 1.1 (JMS 1.1 era). Since the project now uses jakarta.jms (Jakarta Messaging 3.1), the metadata must match. - getJMSVersion(): "1.1" → "3.1" - getJMSMajorVersion(): 1 → 3 * fix(client): use correct exception types per Jakarta Messaging spec (#1722) (#1724) (#1719) Several methods threw wrong exception types, causing TCK failures: - MessageProducer.send() with null destination on an unbound producer threw UnsupportedOperationException instead of InvalidDestinationException - JMSProducer.send() with null message threw NPE instead of MessageFormatRuntimeException - checkClientIDWasManuallySpecified() threw JMSException instead of jakarta.jms.IllegalStateException for durable subscribers without a client ID * fix(client): validate inputs before UnsupportedOperationException in shared consumer methods (#1719) The shared consumer methods (createSharedConsumer, createSharedDurableConsumer) threw UnsupportedOperationException immediately without validating inputs. Per the JMS spec, parameter validation must happen first: - Session: null topic now throws InvalidDestinationException, invalid selector now throws InvalidSelectorException - JMSContext: null topic now throws InvalidDestinationRuntimeException This fixes the TCK invalidDestinationExceptionTests and invalidSelectorExceptionTopicTests for Session, and the corresponding JMSContext tests. fix(client): always include JMSXDeliveryCount in message property names (#1720) getPropertyNames() only included JMSXDeliveryCount when redeliveryCounter != 0. Since JMSXDeliveryCount = redeliveryCounter + 1, it is always >= 1 on a received message and should always be enumerated. The TCK sets 17 custom properties and expects getPropertyNames() to return 18 (17 + JMSXDeliveryCount). * fix(tests): the spec requires InvalidDestinationException when passing null topic. So updating the call but we could instead adapt the expected exception. Anyways, this is a placeholder for the tests of the new features for JMS

Message property count off-by-one (17 vs 18 expected) #1720

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions