Mailing-List: contact cxf-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cxf-dev@incubator.apache.org
Received-SPF: pass (herse.apache.org: domain of eoghan.glynn@iona.com
 designates 62.221.12.33 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Injecting the configuration programmatically
Date: Fri, 15 Dec 2006 13:43:06 -0000
Message-ID: <FA1787F64A095C4090E76EBAF8B183E071FB42@owa-emea.iona.com>
Thread-Topic: Injecting the configuration programmatically
Thread-Index: AccgSaex8b9Ki1YNShK2pPwd7eC8YAAA3Pvg
From: "Glynn, Eoghan" <eoghan.glynn@iona.com>
To: <cxf-dev@incubator.apache.org>


> How to register a custom implementation with the bus ?
>=20
> Thanks, Sergey

After you call SpringBusFactory.createBus(...) to create the Bus, use
Bus.setExtension(myConfiurer, Configurer.class) to register your custom
implmentation. The setExtension() API simply put()s into a Map keyed on
Class, so your custom configurer will just overwrite the standard one
previously registered by createBus().

One caveat though ... make sure your Configurer is registered *before*
your app does anything that would require the particular Bean with
programmatically injected properties to be instantiated. For example,
suppose the Bean in question was the HTTPListenerConfigBean ...
obviously your configurer will have to available when the first Listener
is launched, e.g. before the first call to Endpoint.publish() [assuming
the JAX-WS model].

Cheers,
Eoghan