[infinispan-dev] 3 XmlConfigurationParser implementations, which one to use?
Manik Surtani
manik at jboss.org
Tue Aug 11 07:53:06 EDT 2009
On 11 Aug 2009, at 12:52, Vladimir Blagojevic wrote:
> On 8/11/09 1:39 PM, Manik Surtani wrote:
>>
>> Wasn't this about the default Transport impl, which is the
>> JGroupsTransport? :) From Galder's original email:
>>
>>> For example: If XmlConfigurationParserImpl found a transport
>>> element but
>>> transport class, it gave JGroupsTransport as default, hence a
>>> cluster
>>> channel would be created. However, parsing via
>>> InfinispanConfiguration,
>>> if no transportClass has been defined, no cluster channel is
>>> created.
>>
>> Basically if someone specifies <transport /> but does not specify
>> the transportClass attribute, it should still default to the
>> JGroupsTransport - since that is the sensible default.
>>
> Resolved and committed. Don't blame for for being slow. I just spent
> 10 days on a beach :)
LOL! No worries dude.
--
Manik Surtani
manik at jboss.org
Lead, Infinispan
Lead, JBoss Cache
http://www.infinispan.org
http://www.jbosscache.org
More information about the infinispan-dev
mailing list