Should the async dispatcher queues be distributed?

Question

I have a WLI application with several JPDs in it. So, Workshop automatically
          creates AsyncDispatcher and AsyncDispatcher_error queues for it. The
          question is: how should I configure trhese queues in a clustered env? AFAIK,
          it is recomended to deploy WLI queues on each managed server in the cluster.
          Ok, but should I combine, say, AsyncDispather@JMS_auto_1 and
          AsyncDispather@JMS_auto_2 physical distinations into the one AsyncDispather
          distributed destination or not?
          Thanks, Denis.

Answer 1

Same true for Stack. an add(int index) would break
the deffinition of a Stack. so i think Java choose
flexibility. However, i would rather that Stack and
Queue be their own type of class.I think it was just a bad OO. Extending a class to reuse the code. A Stack is not a Vector. The same goes for Properties.
Stack, Queue, Map, Set, Bag, List
for me, none of these are related and should have
diferent API.I agree for the most part. A List can be used to implement a Queue and a Stack. But instead extending List or Collection, they should have used encapsulation for a basic implementation.
The JDK tends to not use encapsulation very well.