Re: [infinispan-dev] Removal of AS7 compatibility parsers
Can't we converge on one format in the future?
As any converted or dual parser will have it's own set of bugs.
What we could do in the short time is a function which dumps the full
configuration; I'm quite fond of this capability in JGroups to dump
all its stack configuration as an XML, so I added an option in
Hibernate Search to dump it in the logs.
Sanne
On 18 April 2013 18:00, Dennis Reed <dereed(a)redhat.com> wrote:
From a support standpoint, I'd prefer the converters.
It should be easier to debug any issues specific to one configuration
parser.
(It would have been MUCH better to only have one configuration format
for everything, but it's too late for that now...)
-Dennis
On 04/18/2013 02:57 AM, Tristan Tarrant wrote:
> Hi all,
>
> during the 5.2 cycle I added some parsers which enabled reading in the
> infinispan subsystem configuration from AS7/JDG/EAP. While the parsers
> are actually fine, we are still not able to parse the jgroups and
> threads subsystem configuration which are essential elements of a full
> configuration. While I do have some uncommitted work towards making
> these work, I want to throw away all of these parsers and instead add a
> configuration converters (to and from) to the ones we already have. Ray
> Tsang has offered to help with this, and I believe it is a leaner solution.
>
> Opinions please.
>
> Tristan
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev