Apache ActiveMQ Artemis 1.3.0 User Manual
party dependencies. Run ActiveMQ Artemis stand-alone, run it in integrated in your favourite JEE application server, or run it embedded inside your own product. It's up to you. Seamless high availability advantage of this it allows the full set of system functionality to be exposed to the client application. API's like JMS are not normally rich enough to expose all the extra features that most messaging applications interacting with an Apache ActiveMQ Artemis server. User Application 1 is using the JMS API, while User Application 2 is using the core client API directly. You can see from the diagram0 码力 | 247 页 | 1.47 MB | 1 年前3Apache ActiveMQ Artemis 1.2.0 User Manual
party dependencies. Run ActiveMQ Artemis stand-alone, run it in integrated in your favourite JEE application server, or run it embedded inside your own product. It's up to you. Seamless high availability advantage of this it allows the full set of system functionality to be exposed to the client application. API's like JMS are not normally rich enough to expose all the extra features that most messaging applications interacting with an Apache ActiveMQ Artemis server. User Application 1 is using the JMS API, while User Application 2 is using the core client API directly. You can see from the diagram0 码力 | 244 页 | 1.46 MB | 1 年前3Apache ActiveMQ Artemis 1.1.0 User Manual
party dependencies. Run ActiveMQ Artemis stand-alone, run it in integrated in your favourite JEE application server, or run it embedded inside your own product. It's up to you. Seamless high availability advantage of this it allows the full set of system functionality to be exposed to the client application. API's like JMS are not normally rich enough to expose all the extra features that most messaging applications interacting with an Apache ActiveMQ Artemis server. User Application 1 is using the JMS API, while User Application 2 is using the core client API directly. You can see from the diagram0 码力 | 234 页 | 1.40 MB | 1 年前3Apache ActiveMQ Artemis 1.5.5 User Manual
party dependencies. Run ActiveMQ Artemis stand-alone, run it in integrated in your favourite JEE application server, or run it embedded inside your own product. It's up to you. Seamless high availability advantage of this it allows the full set of system functionality to be exposed to the client application. API's like JMS are not normally rich enough to expose all the extra features that most messaging applications interacting with an Apache ActiveMQ Artemis server. User Application 1 is using the JMS API, while User Application 2 is using the core client API directly. You can see from the diagram0 码力 | 399 页 | 1.61 MB | 1 年前3Apache ActiveMQ Artemis 1.5.1 User Manual
party dependencies. Run ActiveMQ Artemis stand-alone, run it in integrated in your favourite JEE application server, or run it embedded inside your own product. It's up to you. Seamless high availability advantage of this it allows the full set of system functionality to be exposed to the client application. API's like JMS are not normally rich enough to expose all the extra features that most messaging applications interacting with an Apache ActiveMQ Artemis server. User Application 1 is using the JMS API, while User Application 2 is using the core client API directly. You can see from the diagram0 码力 | 399 页 | 1.61 MB | 1 年前3Apache ActiveMQ Artemis 1.5.0 User Manual
party dependencies. Run ActiveMQ Artemis stand-alone, run it in integrated in your favourite JEE application server, or run it embedded inside your own product. It's up to you. Seamless high availability advantage of this it allows the full set of system functionality to be exposed to the client application. API's like JMS are not normally rich enough to expose all the extra features that most messaging applications interacting with an Apache ActiveMQ Artemis server. User Application 1 is using the JMS API, while User Application 2 is using the core client API directly. You can see from the diagram0 码力 | 393 页 | 1.60 MB | 1 年前3Apache ActiveMQ Artemis 1.5.3 User Manual
party dependencies. Run ActiveMQ Artemis stand-alone, run it in integrated in your favourite JEE application server, or run it embedded inside your own product. It's up to you. Seamless high availability advantage of this it allows the full set of system functionality to be exposed to the client application. API's like JMS are not normally rich enough to expose all the extra features that most messaging applications interacting with an Apache ActiveMQ Artemis server. User Application 1 is using the JMS API, while User Application 2 is using the core client API directly. You can see from the diagram0 码力 | 243 页 | 1.31 MB | 1 年前3Apache ActiveMQ Artemis 1.4.0 User Manual
party dependencies. Run ActiveMQ Artemis stand-alone, run it in integrated in your favourite JEE application server, or run it embedded inside your own product. It's up to you. Seamless high availability advantage of this it allows the full set of system functionality to be exposed to the client application. API's like JMS are not normally rich enough to expose all the extra features that most messaging applications interacting with an Apache ActiveMQ Artemis server. User Application 1 is using the JMS API, while User Application 2 is using the core client API directly. You can see from the diagram0 码力 | 389 页 | 1.59 MB | 1 年前3Apache ActiveMQ Artemis 1.5.2 User Manual
party dependencies. Run ActiveMQ Artemis stand-alone, run it in integrated in your favourite JEE application server, or run it embedded inside your own product. It's up to you. Seamless high availability advantage of this it allows the full set of system functionality to be exposed to the client application. API's like JMS are not normally rich enough to expose all the extra features that most messaging applications interacting with an Apache ActiveMQ Artemis server. User Application 1 is using the JMS API, while User Application 2 is using the core client API directly. You can see from the diagram0 码力 | 399 页 | 1.61 MB | 1 年前3Apache ActiveMQ Artemis 2.1.0 User Manual
party dependencies. Run ActiveMQ Artemis stand-alone, run it in integrated in your favourite JEE application server, or run it embedded inside your own product. It's up to you. Seamless high availability advantage of this it allows the full set of system functionality to be exposed to the client application. API's like JMS are not normally rich enough to expose all the extra features that most messaging applications interacting with an Apache ActiveMQ Artemis server. User Application 1 is using the JMS API, while User Application 2 is using the core client API directly. You can see from the diagram0 码力 | 407 页 | 1.93 MB | 1 年前3
共 48 条
- 1
- 2
- 3
- 4
- 5