java - JMS interfaces and implementations -


The JMS API declares many common and solid interfaces (e.g., connection versus Qi connection). It is documented that the best practice is to use normal interfaces (eg session and queue session). If my application is using both queues and topics and I am going normal, then this is: connection -> session -> subject / line, and support of all JMS implementations (TBK, Weblog, WebSpace etc ...) Do I think that using normal institutions will work for both types of out-of-the-box (queue and subject)?

To emphasize my point: Can I assume that all applicants apply Javascript? Can the connection interface work in both common types of cases?

thanks, boy

Java.jmx.Connection not optional in JMS 1.1 specification , So a valid implementation should be done. Most optional accessories in JM are listed in Chapter 8 "JMS Application Server Utilities".

A notable issue is that according to the connection device for exception list is optional.

I think the main point here is that you can actually review with your design and implementation imagery that you are not dependent on any alternative facilities and you must be properly portable Safe in


Comments

Popular posts from this blog

oracle - The fastest way to check if some records in a database table? -

php - multilevel menu with multilevel array -

jQuery UI: Datepicker month format -