BTW I have this in trunk now - you would do something like:
<transport ....>
<properties>
<property name="channelLookup"
value="com.blah.MyJGroupsChannelLookup" />
</properties>
</transport>
to pass in a ChannelLookup, which would need to implement
http://fisheye.jboss.org/browse/Infinispan/trunk/core/src/main/java/org/i...
Cheers
Manik
On 1 Oct 2009, at 11:12, Manik Surtani wrote:
On 30 Sep 2009, at 13:23, Galder Zamarreno wrote:
>
>
> On 09/30/2009 01:42 PM, Mircea Markus wrote:
>> Can't we use an
>> interface JGroupsChannelLookup {
>> JChannel lookupChannel();
>> }
>> This can be specified as a parameter to the trasport
>> <property name="txLookup"
value="org.xyz.MySpecificLookup"/>
>>
>> we are using 2 lookups already (TM, MBeanServerLookup) and this
>> would
>> be consistent with the code base.
>> I would stick with the lookup within JGroupsTransport and not within
>> the TransportLookup, as this seems rather particular.
>
> +1.
>
> It's something like this what I had in mind with my previous email
> but
> forgot of how complex JGroupsTransport and that it does much more
> than
> only create the JChannel.
Makes sense. Brian, thoughts? Does this work for you?
Cheers
Manik
--
Manik Surtani
manik(a)jboss.org
Lead, Infinispan
Lead, JBoss Cache
http://www.infinispan.org
http://www.jbosscache.org
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Manik Surtani
manik(a)jboss.org
Lead, Infinispan
Lead, JBoss Cache
http://www.infinispan.org
http://www.jbosscache.org