ricardlf wrote:
Gordon Sim wrote:
Do you need to declare them at 'run time'? Or could they be setup as a
configuration step prior to starting the application?
I need to declare them at run time.
Can you give some more detail on the pattern in use? Getting good use
cases helps ensure the design evolves to better support them.
Please, could you post an example code
showing how to do that?
You can cause exchanges to be declared simply by altering your binding
url and creating a consumer or publisher. E.g. look at the direct
example for jms[1] and modify the direct.properties to change from using
amq.direct to some other exchange[2]. Now if you run the direct producer
or consumer the exchange will be created.
--Gordon
[1] I.e. the examples located in
qpid/java/client/example/src/main/java/org/apache/qpid/example/jmsexample/direct
[2] E.g. apply the following patch:
diff -up
org/apache/qpid/example/jmsexample/direct/direct.properties.original
org/apache/qpid/example/jmsexample/direct/direct.properties
--- org/apache/qpid/example/jmsexample/direct/direct.properties.original
2009-07-28 08:18:01.000000000 -0400
+++ org/apache/qpid/example/jmsexample/direct/direct.properties
2009-07-28 08:18:37.000000000 -0400
@@ -24,4 +24,4 @@ connectionfactory.qpidConnectionfactory
# Register an AMQP destination in JNDI
# destination.[jniName] = [BindingURL]
-destination.directQueue =
direct://amq.direct//message_queue?routingkey='routing_key'
\ No newline at end of file
+destination.directQueue =
direct://my-direct-exchange//message_queue?routingkey='routing_key'
\ No newline at end of file
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:users-subscr...@qpid.apache.org
