in situations where client's don't clean up their own sessions. Distribute full Jakarta Messaging 3.0 client in the lib/client directory along with a new example of how to use it in examples/features/standard/queue- management method to create a core bridge using JSON-based configuration input. Jakarta Messaging 2.0 & 3.0 artifacts for Jakarta EE 8 & 9 respectively. 2.16.0 Full release notes. Highlights: Configurable implementations which are a fully compliant with JMS 1.1 & 2.0 as well as Jakarta Messaging 2.0 & 3.0. System specific APIs Many systems provide their own programmatic API for which to interact with

in situations where client's don't clean up their own sessions. Distribute full Jakarta Messaging 3.0 client in the lib/client directory along with a new example of how to use it in examples/features/standard/queue- management method to create a core bridge using JSON-based configuration input. Jakarta Messaging 2.0 & 3.0 artifacts for Jakarta EE 8 & 9 respectively. 2.16.0 Full release notes. Highlights: Configurable implementations which are a fully compliant with JMS 1.1 & 2.0 as well as Jakarta Messaging 2.0 & 3.0. System specific APIs Many systems provide their own programmatic API for which to interact with

in situations where client's don't clean up their own sessions. Distribute full Jakarta Messaging 3.0 client in the lib/client directory along with a new example of how to use it in examples/features/standard/queue- management method to create a core bridge using JSON-based configuration input. Jakarta Messaging 2.0 & 3.0 artifacts for Jakarta EE 8 & 9 respectively. 2.16.0 Full release notes. Highlights: Configurable implementations which are a fully compliant with JMS 1.1 & 2.0 as well as Jakarta Messaging 2.0 & 3.0. System specific APIs Many systems provide their own programmatic API for which to interact with

implementations which are a fully compliant with JMS 1.1 & 2.0 as well as Jakarta Messaging 2.0 & 3.0. 3.6.2. System specific APIs Many systems provide their own programmatic API for which to interact This client is also compliant with the Jakarta Messaging 2.0 specification. 3. Jakarta Messaging 3.0 client API. This is essentially the same as the JMS 2.0 API. The only difference is the package names situations where client’s don’t clean up their own sessions. • Distribute full Jakarta Messaging 3.0 client in the lib/client directory along with a new example of how to use it in examples/features

implementations which are a fully compliant with JMS 1.1 & 2.0 as well as Jakarta Messaging 2.0 & 3.0. 3.6.2. System specific APIs Many systems provide their own programmatic API for which to interact This client is also compliant with the Jakarta Messaging 2.0 specification. 3. Jakarta Messaging 3.0 client API. This is essentially the same as the JMS 2.0 API. The only difference is the package names situations where client’s don’t clean up their own sessions. • Distribute full Jakarta Messaging 3.0 client in the lib/client directory along with a new example of how to use it in examples/features

implementations which are a fully compliant with JMS 1.1 & 2.0 as well as Jakarta Messaging 2.0 & 3.0. 3.6.2. System specific APIs Many systems provide their own programmatic API for which to interact This client is also compliant with the Jakarta Messaging 2.0 specification. 3. Jakarta Messaging 3.0 client API. This is essentially the same as the JMS 2.0 API. The only difference is the package names situations where client’s don’t clean up their own sessions. • Distribute full Jakarta Messaging 3.0 client in the lib/client directory along with a new example of how to use it in examples/features

implementations which are a fully compliant with JMS 1.1 & 2.0 as well as Jakarta Messaging 2.0 & 3.0. 3.6.2. System specific APIs Many systems provide their own programmatic API for which to interact This client is also compliant with the Jakarta Messaging 2.0 specification. 3. Jakarta Messaging 3.0 client API. This is essentially the same as the JMS 2.0 API. The only difference is the package names situations where client’s don’t clean up their own sessions. • Distribute full Jakarta Messaging 3.0 client in the lib/client directory along with a new example of how to use it in examples/features

implementations which are a fully compliant with JMS 1.1 & 2.0 as well as Jakarta Messaging 2.0 & 3.0. 3.6.2. System specific APIs Many systems provide their own programmatic API for which to interact This client is also compliant with the Jakarta Messaging 2.0 specification. 3. Jakarta Messaging 3.0 client API. This is essentially the same as the JMS 2.0 API. The only difference is the package names situations where client’s don’t clean up their own sessions. • Distribute full Jakarta Messaging 3.0 client in the lib/client directory along with a new example of how to use it in examples/features

implementations which are a fully compliant with JMS 1.1 & 2.0 as well as Jakarta Messaging 2.0 & 3.0. 3.6.2. System specific APIs Many systems provide their own programmatic API for which to interact This client is also compliant with the Jakarta Messaging 2.0 specification. 3. Jakarta Messaging 3.0 client API. This is essentially the same as the JMS 2.0 API. The only difference is the package names situations where client’s don’t clean up their own sessions. • Distribute full Jakarta Messaging 3.0 client in the lib/client directory along with a new example of how to use it in examples/features

implementations which are a fully compliant with JMS 1.1 & 2.0 as well as Jakarta Messaging 2.0 & 3.0. 3.6.2. System specific APIs Many systems provide their own programmatic API for which to interact This client is also compliant with the Jakarta Messaging 2.0 specification. 3. Jakarta Messaging 3.0 client API. This is essentially the same as the JMS 2.0 API. The only difference is the package names situations where client’s don’t clean up their own sessions. • Distribute full Jakarta Messaging 3.0 client in the lib/client directory along with a new example of how to use it in examples/features