Return-Path: 
 <camel-user-return-933-apmail-activemq-camel-user-archive=activemq.apache.org@activemq.apache.org>
Delivered-To: apmail-activemq-camel-user-archive@locus.apache.org
Received: (qmail 85509 invoked from network); 18 Jan 2008 15:57:39 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 18 Jan 2008 15:57:39 -0000
Received: (qmail 23654 invoked by uid 500); 18 Jan 2008 15:57:29 -0000
Delivered-To: apmail-activemq-camel-user-archive@activemq.apache.org
Received: (qmail 23633 invoked by uid 500); 18 Jan 2008 15:57:29 -0000
Mailing-List: contact camel-user-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:camel-user-help@activemq.apache.org>
List-Unsubscribe: <mailto:camel-user-unsubscribe@activemq.apache.org>
List-Post: <mailto:camel-user@activemq.apache.org>
List-Id: <camel-user.activemq.apache.org>
Reply-To: camel-user@activemq.apache.org
Delivered-To: mailing list camel-user@activemq.apache.org
Received: (qmail 23621 invoked by uid 99); 18 Jan 2008 15:57:29 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Jan 2008 07:57:29 -0800
X-ASF-Spam-Status: No, hits=2.6 required=10.0
	tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Jan 2008 15:57:16 +0000
Received: from isper.nabble.com ([192.168.236.156])
	by kuber.nabble.com with esmtp (Exim 4.63)
	(envelope-from <lists@nabble.com>)
	id 1JFtae-0002Rm-Gv
	for camel-user@activemq.apache.org; Fri, 18 Jan 2008 07:57:08 -0800
Message-ID: <14952115.post@talk.nabble.com>
Date: Fri, 18 Jan 2008 07:57:08 -0800 (PST)
From: DominicTulley <dominic.tulley@telelogic.com>
To: camel-user@activemq.apache.org
Subject: Re: Configuring a Routebuilder from activemq.xml file?
In-Reply-To: <14951653.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Nabble-From: dominic.tulley@telelogic.com
References: <14923839.post@talk.nabble.com>
 <f1c427510801171012w564e0dbawf0ceed18fc5256cc@mail.gmail.com>
 <f1c427510801171017g26fcae56re4dc1bb5a3c9e674@mail.gmail.com>
 <ec6e67fd0801171137l8a75cddh4d442312d3967fc4@mail.gmail.com>
 <f1c427510801180251wa041333ne8358b291611e3f4@mail.gmail.com>
 <14951653.post@talk.nabble.com>
X-Virus-Checked: Checked by ClamAV on apache.org


Then I had another look.  I moved my bean definitions to be after the
<broker> entry and now it seems to work (at least, it started up!).

I'll take a pop at actually making it route some messages now and see if
it's really all as live as it looks.

Thanks,

-Dominic


DominicTulley wrote:
> 
> I gave this suggestion a go, so that I had the following:
> 
>   <bean id="routing-config" class="org.dominic.RoutingConfig" >
>      <property name="something" value="23" />
>   </bean>
>   
>   <bean id="route-builder" class="org.dominic.MyFirstRouter" >
>      <property name="config" ref="routing-config" />
>   </bean>  
>   
>   <bean id="camel" class="org.apache.camel.spring.CamelContextFactoryBean"
> >
>      <property name="routeBuilder" ref="route-builder" />
>   </bean>
> 
> I also removed <camelcontext> from the file.  Unfortunately this doesn't
> seem to quite work.
> I get errors indicating that a broker already exists (see below). 
> However, I don't have another broker running so I presume that AMQ is
> deciding to make two camel instances for some reason.
> It's a shame because it seemed quite a neat solution for now!
> 
> WARN  ManagementContext              - Failed to start jmx connector:
> Cannot bind to URL [rmi://localhost:1099/jmxrmi]:
> javax.naming.NameAlreadyBoundException:
> jmxrmi [Root exception is java.rmi.AlreadyBoundException: jmxrmi]
> ERROR BrokerService                  - Failed to start ActiveMQ JMS
> Message Broker. Reason: javax.management.InstanceAlreadyExistsException:
> org.apache.activemq
> :BrokerName=localhost,Type=Broker
> javax.management.InstanceAlreadyExistsException:
> org.apache.activemq:BrokerName=localhost,Type=Broker
>         at
> com.sun.jmx.mbeanserver.RepositorySupport.addMBean(RepositorySupport.
> java:452)
> 
> 
> 
> RomKal wrote:
>> 
>>> A RouteBuilder is not necessarily gonna be XML marshallable via JAXB;
>>> so we might just wanna refer to RouteBuilder instances by ID in the
>>> XML.
>> 
>> I believe we should allow this in namespace notation.
>> 
>> But just to solve Dominic's problem maybe instead of creating our
>> context via <camelContext> we could simply do
>> 
>> <bean class="org.apache.camel.spring.CamelContextFactoryBean">
>> <property name="routeBuilder" ref="myConfiguredBuilder/>
>> </bean>
>> 
>> It should work, shouldn't it?
>> 
>> Romek
>> 
>> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Configuring-a-Routebuilder-from-activemq.xml-file--tp14923839s22882p14952115.html
Sent from the Camel - Users mailing list archive at Nabble.com.