[infinispan-dev] 3 XmlConfigurationParser implementations, which one to use?

[Vladimir Blagojevic]

InfinispanConfiguration is JAXB based parser. I will remove the other 
two and all related classes.
The details you noticed Galder are intricacies of JAXB parsing. We 
should always specify class from now on. I will still look if it is 
possible to resolve this and have 100% compatibility with previous 
parser - but believe me it is not always possible.

On 8/4/09 1:59 PM, Manik Surtani wrote:
> A question for Vladimir, I believe.
>
> On 4 Aug 2009, at 11:10, Galder Zamarreno wrote:
>
>    
>> Hi,
>>
>> There's a bit of a mess now with regards to XmlConfigurationParser
>> implementations. There're now 3 of them:
>>
>> AutomatedXmlConfigurationParserImpl
>> InfinispanConfiguration
>> XmlConfigurationParserImpl
>>
>> Which one should we be using to parse XML configuration files from
>> unit
>> tests?
>>
>> The reason I'm asking is because parsing via InfinispanConfiguration
>> returns different results to parsing via previous
>> XmlConfigurationParserImpl.
>>
>> 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.
>>
>> We need to keep one and deprecate the others making sure we note
>> things
>> like this, i.e. if no transport class is defined, by default we use
>> JGroupsTransport (something which IMO makes a lot of sense)
>>
>> Cheers,
>> -- 
>> Galder Zamarreño
>> Sr. Software Engineer
>> Infinispan, JBoss Cache
>> _______________________________________________
>> infinispan-dev mailing list
>> infinispan-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>>      
>
> --
> Manik Surtani
> manik at jboss.org
> Lead, Infinispan
> Lead, JBoss Cache
> http://www.infinispan.org
> http://www.jbosscache.org
>
>
>
>
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>    

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/infinispan-dev/attachments/20090811/ecff5e86/attachment-0002.html