Hello again
I've actually found out that the Registry needs to be overriden in the
RouteBuilder.configure() method.
Getting closer... :)
S. Ali Tokmen
[EMAIL PROTECTED]
Office: +33 4 76 29 76 19
GSM: +33 66 43 00 555
Bull, Architect of an Open World TM
http://www.bull.com
S. Ali Tokmen a écrit :
Hello
Time for me to be more elaborate, then... :)
When we're doing a Repository service, our aim is to link logical URLs
to technical URLs.
For example:
* The logical URL reference:sampleTopic has as technical
correspondent jms:topic:sampleTopic?disableReplyTo=true
* Therefore, if the user writes reference:sampleTopic in its
camel-context.xml file, CAMEL should act exactly as if
jms:topic:sampleTopic?disableReplyTo=true was written
What I've seen in CAMEL is that JNDI on JMS also does a similar job:
* The default JMS implementation requires the JMS worker names to be
written (for example, jms:queue:#0.0.1023)
* To replace that with a JNDI lookup, we need to set the
destinationResolver property of the JmsComponent bean with a
JndiDestinationResolver bean (in camel-context.xml)
* Once that is done, writing jms:queue:sampleQueue becomes
equivalent to writing jms:queue:#0.0.1023
And that's why I'm mentioning the destinationResolvers...
Do you think I'm going in the wrong direction?
Cheers
S. Ali Tokmen
[EMAIL PROTECTED]
Office: +33 4 76 29 76 19
GSM: +33 66 43 00 555
Bull, Architect of an Open World TM
http://www.bull.com
Claus Ibsen a écrit :
On Thu, Nov 20, 2008 at 11:46 AM, S. Ali Tokmen
<[EMAIL PROTECTED]> wrote:
Hello
After some tests, I have the impression that the real property to
look after
is the "destinationResolver" property. Do you think that's expected?
Could you elaborate what you mean, eg. write some more?
Which destinationResolver. I can not find destinationResolver in Camel.
