[infinispan-dev] 3 XmlConfigurationParser implementations, which one to use?
Vladimir Blagojevic
vblagoje at redhat.com
Tue Aug 11 07:52:30 EDT 2009
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 :)
More information about the infinispan-dev
mailing list