Hi, This option helps in deployment time, but if I want to load several implementations and use in runtime different implementations in different flows, there is still a problem.
Thanks, Igor On Wed, 2005-04-27 at 14:39, Knut Wannheden wrote: > Igor, > > If you're using HiveMind 1.1 there is yet another option. You can make > the <implementation> elements conditional using an "if" attribute. The > value of this attribute is a conditional expression which basically is > a boolean expression in which you reference class names and system > properties. Check here for more information and examples: > http://jakarta.apache.org/hivemind/current/conditional.html. > > HTH, > > --knut > > On 4/27/05, Johan Lindquist <[EMAIL PROTECTED]> wrote: > > Two options - have two service points (same service interface is allowed, > > just name the service point will be have to differ) or use the override > > functionality (http://jakarta.apache.org/hivemind/current/override.html) > > > > Cheers, > > > > Johan > > > > On 27 Apr 2005 14:33:46 +0300, Igor Laberov <[EMAIL PROTECTED]> wrote: > > > > > Hi again, > > > In our application we want to have multiple implementation classes for > > > one service. So .xml file will look like > > > <service-point id="Part" /> > > > <implementation service-id="Part"> > > > <create-instance class="one.PartImpl"/> > > > </implementation> > > > <implementation service-id="Part"> > > > <create-instance class="two.PartImpl"/> > > > </implementation> > > > > > > At startup user will choose implementation that he want to work with > > > (and its id will be stored), and later user operations will be > > > associated with selected implementation. > > > > > > As I see from RegistryBuilder code, it is not allowed to have 2 > > > implementation. > > > Can you point me to other way having several service implementation? Or > > > may be I can override some system service? > > > > > > Thank you, > > > Igor Laberov > > > Qlusters, Inc. > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > -- > > you too? > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
