Hi Guillaume, Thanks, that works great. I had tried the component attribute, but I forgot or didn't realise about the "#" ... it makes all the difference.
John Hurst -----Original Message----- From: Guillaume Nodet [mailto:[EMAIL PROTECTED] Sent: Wednesday, 30 November 2005 21:10 To: [email protected] Subject: Re: [servicemix-user] Can an activationSpec refer to another bean as the <component>? You could try <sm:actionSpec component="#myBean" ... /> ... <bean name="myBean" ... It should work. Guillaume Nodet HURST, John B wrote: > Hi, > > All the ServiceMix config XML examples I've found have activationSpec > elements defined like this: > > <sm:activationSpec ...> > > <sm:component> > > <bean .../> > > </sm:component> > > </sm:activationSpec> > > That is, the <sm:component> element contains a nested anonymous bean. > > Is there a way to make this element refer to a bean elsewhere, or give > it a name otherwise so that other beans can refer to it? > > Note: I'm not talking about the properties of the bean, which commonly > refer to other named beans. I want other beans to be able to refer to > the bean that is the component. (In my particular case I want a Quartz > scheduler to schedule a polling service.) > > BTW, I've found I can do this easily using the "regular" Spring syntax > in my config file - can I do it with the XBean enhanced syntax? > > Regards > > John Hurst > > Wellington, New Zealand (well, Melbourne, Australia today) > > > ______________________________________________________________________ > This email has been scanned by the MessageLabs Email Security System. > For more information please visit http://www.messagelabs.com/email > ______________________________________________________________________ ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________
