在通常情况下，网桥队列名称反映了WebSphereMQ目的地队列的名称。
Under normal circumstances, the bridge queue names reflect the name of the WebSphere MQ destination queue.
现在，我们已经在消息引擎中创建了一个队列目的地，如图19所示。
We have now set up a queue destination inside the message engine, as shown in Figure 19.
在大多数情况下，应用程序可以直接使用目的地对象，不管它是表示队列还是主题，并且仅根据需要生成或使用消息。
In most cases, the application can simply use the destination object without regard to whether it represents a queue or topic, and simply produce or consume messages as appropriate.
目的地是一些可以具有服务端点、队列或者主题的行为的逻辑地址。
Destinations are logical addresses which can have the behavior of a service endpoint, a queue, or a topic.
队列是这样一个目的地：生产者向它发送消息，接收者从中取消息。
A queue is a destination to which a producer sends messages and from which the receiver takes messages.
为其余队列重复上述步骤，并从总线选择匹配的物理目的地。
Repeat these steps for the remaining queues, selecting the matching physical destination from the bus.
这里隐含着一个难以察觉但非常重要的要求，在设计时，您必须知道目的地是队列还是主题。
A more subtle but important implication is that you had to know whether the destination was a queue or a topic at design time.
这包括诸如服务集成总线、JMS提供程序、队列、主题、目的地等资源。
This includes resources such as service integration buses, JMS providers, queues, topics, destinations, and so on.
新的队列目的地将显示在总线的目的地列表中。
The new queue destination will appear in the list of destinations for the bus.
换句话说就是，JMS提供者可以向消息的发送方保证将消息发送到目的地(一个队列或主题)，并且是一次性发送。
In other words, the JMS provider can assure a message's sender that it was delivered to it's destination (a queue or topic) once and only once.
jms目的地类型：队列或主题。
您可以把目的地看作是队列及主题的泛化。
You can think of destinations as a generalization of a queue and topic.
不过，队列和主题在传输级别上有本质的不同，所以必须将任何给定目的地的注册项专门定义为队列或主题。
However, queues and topics are inherently different at the transport level and so the registry entry for any given destination must be specifically defined as either a queue or topic.
队列目的地，可以配置为进行点到点消息传递的目的地。
Queue destinations are destinations that can be configured for point-to-point messaging.
此目的地可以为主题或队列，具体取决于应用程序的域。
This destination might be a topic or a queue, depending on the application's domain.
常规的队列目的地可配置为从外部总线接收消息。
A regular queue destination can be configured to receive messages from a foreign bus.
设置队列的jms目的地。
第3部分描述了队列目的地的创建过程。
在上面的模型中，可以看到一个目的地(例如一个队列)唯一地分配给一个总线成员。
In the model above, it could be seen that a Destination for example, a Queue is uniquely assigned to a Bus Member.
拥有目的地和总线后，您可以创建连接工厂、jms队列和激活规范。
Now that we have the destinations and the bus, you can create the connection factories, the JMS queues, and the activation specifications.
一个入站服务的“队列”目的地。
将在不同的对象中创建两个队列类型的目的地
Two queue type destinations will be created in separate objects
我们需要创建总线目的地来接收放在WebSphereMQ中的远程队列中的消息。
We need a bus destination to receive the messages placed onto the remote queue in WebSphere MQ.
ServletWriteQueue（清单1）将产生发送到指定队列目的地的所有类型的JMS消息。
The servlet WriteQueue (Listing 1), produces all kinds of JMS messages that are sent to a designated queue destination.
我们在SIBus中创建了一个新的外部目的地，来表示WebSphereMQ中的响应队列。
We create a new foreign destination on the SIBus that represents the response queue in WebSphere MQ.
由于您的Web服务还接受使用JMS的请求，因此需要创建一个总线、两个用于传入和应答的队列目的地和一个用于消息驱动Bean (Message Driven Bean,mdb)的激活规范。
Because your Web service also accepts requests using the JMS, you need to create a bus, two queue destinations for incoming and replies, and an activation spec for the message driven bean (MDB).
点到点的目的地是队列。
您需要创建队列目的地，并定义JCA激活规范，以启用在安装示例应用程序时将看到的消息驱动Bean。
You need to create a queue destination and define a JCA activation spec for enabling the message-driven bean that you will see when you install the sample application.
接下来，创建激活规范，以将MDB连接到队列目的地。
Next, create an activation specification to connect your message-driven bean to the queue destination.
WebSphereApplicationServerSI总线除提供其他功能以外，还允许您定义应用程序用于发送或检索消息的目的地(如队列或主题)。
A WebSphere application Server SI Bus lets you to define, among other things, destinations (such as queues or topics) that applications can use to send or retrieve messages.
应用推荐