Apache ActiveMQ Artemis 2.26.0 User Manualquestions related to the use or development of Apache ActiveMQ Artemis please use one of our mailing lists. Versions 8 Versions This chapter provides the following information for each release: A link Messaging 3.0 client API. This is essentially the same as the JMS 2.0 API. The only difference is the package names use jakarta insead of javax . This difference was introduced due to the move from Oracle's Bootstrap dependencies like logging handlers must be accessible by the log manager at boot time. Package the dependency in a jar and put it on the boot classpath before of log manager jar. This can be0 码力 | 487 页 | 6.28 MB | 1 年前3
Apache ActiveMQ Artemis 2.4.0 User Manualto the new settings as well, as soon as they performs a new security-sensitive operation. Below lists the effects of adding, deleting and updating of an element/attribute within theby parameter config-delete-addresses and config-delete-queues as described in the doc. Below lists the effects of adding, deleting and updating of an element/attribute within the address-settings element element is updated after reloading. To make this happen you need a restart of the broker. Below lists the effects of adding, deleting and updating of an element/attribute within the diverts element, whether 0 码力 | 265 页 | 2.84 MB | 1 年前3
Apache ActiveMQ Artemis 2.3.0 User Manualto the new settings as well, as soon as they performs a new security-sensitive operation. Below lists the effects of adding, deleting and updating of an element/attribute within theparameter config-delete-addresses and config-delete- queues as described in the doc. Below lists the effects of adding, deleting and updating of an element/attribute within the address-settings element is updated after reloading. To make this happen you need a restart of the broker. Below lists the effects of adding, deleting and updating of an element/attribute within the diverts element, 0 码力 | 420 页 | 3.03 MB | 1 年前3
Apache ActiveMQ Artemis 2.6.0 User Manualbroker plugins, JDBC drivers, password decoders, etc. must be accessible by the broker at runtime. Package the dependency in a jar, and put it on the broker's classpath. This can be done by placing the to the new settings as well, as soon as they performs a new security-sensitive operation. Below lists the effects of adding, deleting and updating of an element/attribute within theparameter config-delete-addresses and config-delete- queues as described in the doc. Below lists the effects of adding, deleting and updating of an element/attribute within the address-settings 0 码力 | 445 页 | 3.14 MB | 1 年前3
Apache ActiveMQ Artemis 2.30.0 User Manualquestions related to the use or development of Apache ActiveMQ Artemis please use one of our mailing lists. Versions 8 Versions This chapter provides the following information for each release: A link Messaging 3.0 client API. This is essentially the same as the JMS 2.0 API. The only difference is the package names use jakarta insead of javax . This difference was introduced due to the move from Oracle's Bootstrap dependencies like logging handlers must be accessible by the log manager at boot time. Package the dependency in a jar and put it on the boot classpath before of log manager jar. This can be0 码力 | 500 页 | 6.37 MB | 1 年前3
Apache ActiveMQ Artemis 2.28.0 User Manualquestions related to the use or development of Apache ActiveMQ Artemis please use one of our mailing lists. Versions 8 Versions This chapter provides the following information for each release: A link Messaging 3.0 client API. This is essentially the same as the JMS 2.0 API. The only difference is the package names use jakarta insead of javax . This difference was introduced due to the move from Oracle's Bootstrap dependencies like logging handlers must be accessible by the log manager at boot time. Package the dependency in a jar and put it on the boot classpath before of log manager jar. This can be0 码力 | 494 页 | 6.33 MB | 1 年前3
Apache ActiveMQ Artemis 2.29.0 User Manualquestions related to the use or development of Apache ActiveMQ Artemis please use one of our mailing lists. Versions 8 Versions This chapter provides the following information for each release: A link Messaging 3.0 client API. This is essentially the same as the JMS 2.0 API. The only difference is the package names use jakarta insead of javax . This difference was introduced due to the move from Oracle's Bootstrap dependencies like logging handlers must be accessible by the log manager at boot time. Package the dependency in a jar and put it on the boot classpath before of log manager jar. This can be0 码力 | 499 页 | 6.37 MB | 1 年前3
Apache ActiveMQ Artemis 2.24.0 User Manualquestions related to the use or development of Apache ActiveMQ Artemis please use one of our mailing lists. Versions 8 Versions This chapter provides the following information for each release: A link Messaging 3.0 client API. This is essentially the same as the JMS 2.0 API. The only difference is the package names use jakarta insead of javax . This difference was introduced due to the move from Oracle's Bootstrap dependencies like logging handlers must be accessible by the log manager at boot time. Package the dependency in a jar and put it on the boot classpath before of log manager jar. This can be0 码力 | 513 页 | 6.41 MB | 1 年前3
Apache ActiveMQ Artemis 2.25.0 User Manualquestions related to the use or development of Apache ActiveMQ Artemis please use one of our mailing lists. Versions 8 Versions This chapter provides the following information for each release: A link Messaging 3.0 client API. This is essentially the same as the JMS 2.0 API. The only difference is the package names use jakarta insead of javax . This difference was introduced due to the move from Oracle's Bootstrap dependencies like logging handlers must be accessible by the log manager at boot time. Package the dependency in a jar and put it on the boot classpath before of log manager jar. This can be0 码力 | 514 页 | 6.41 MB | 1 年前3
Apache ActiveMQ Artemis 2.11.0 User ManualBootstrap dependencies like logging handlers must be accessible by the log manager at boot time. Package the dependency in a jar and put it on the boot classpath before of log manager jar. This can be broker plugins, JDBC drivers, password decoders, etc. must be accessible by the broker at runtime. Package the dependency in a jar, and put it on the broker's classpath. This can be done by placing the jar to the new settings as well, as soon as they performs a new security-sensitive operation. Below lists the effects of adding, deleting and updating of an element/attribute within the0 码力 | 341 页 | 4.93 MB | 1 年前3
共 46 条
- 1
- 2
- 3
- 4
- 5













