JMS Section Index | Page 7

Should the producing client store data in a message's header or its body?

Is it possible to do RMI-like, request-reply communication with JMS?

Is it possible to turn off message acknowledgment if it is not important for a particular communication scenario?

How does a consumer acknowledge a message from a producer?

Is it possible for a consumer to look ahead at incoming messages? Is there anything for messages similar to the C library's getc() and ungetc() for character streams?

Why is JNDI important anyway?

Which JMS vendors fully support JNDI look-up operations for connection factories and destinations?

Does JMS directly support XML?

How does a client accommodate asynchronous message notifications from the JMS server?

How do you implement a client that publishes to a topic?

How do you implement a client that subscribes to a topic?

How do you implement a client that sends messages via a queue?

How do you implement a client that receives messages via a queue?

How does a client create a topic (or a queue)?

What is the difference between durability and persistence? Both use secondary storage to "hold" messages.

About | Sitemap | Contact